Listeners fail after a lengthy period of being active. ------------------------------------------------------ Key: JBESB-250 URL: http://jira.jboss.com/jira/browse/JBESB-250 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Kevin Conner Fix For: 4.0 "It is really simple, when a service is auto-reloaded via its parameterReloadSecs="10" attribute in the esb-config.xml it sometimes fails to properly go through the self-registration process with the registry. Unfortunately it is not consistent. We'll just need to leave a few listeners running some place to see how they behave over time." "I see this in the logs when it reloads the config (sometimes): [JmsQueueListener] Unregistering this EPR done: creditagency [java] 14:36:10,880 DEBUG [SocketManager] End ReadTask.run [java] 14:36:10,880 DEBUG [UILClientILService] Stopping [java] 14:36:10,880 DEBUG [SocketManager] End WriteTask.run [java] 14:36:10,927 INFO [JmsQueueListener] Unregistering this EPR done: creditagency [java] 14:36:10,942 DEBUG [SocketManager] End ReadTask.run [java] 14:36:10,942 DEBUG [UILClientILService] Stopping [java] 14:36:10,942 DEBUG [SocketManager] End WriteTask.run [java] 14:36:19,348 INFO [JmsQueueListener] Unregistering this EPR, we're going to reload: creditagency so it goes to unregister twice.. the second time we get a stacktrace, since it's already gone. Do we have more then 1 JmsQueueListener thread??" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira