[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-886) Client unable to reconnect to JBoss 1.0.1.SP4 after restart
[ http://jira.jboss.com/jira/browse/JBMESSAGING-886?page=all ]
Ben Anderson updated JBMESSAGING-886:
-------------------------------------
Attachment: ReconnectTest.java
Test case to demonstrate the issue (see forum post for instructions). Note that the timing
of the server restart appears to be a factor. Reproducing the problem is more likely to
occur if the server is restarted while the test cases is still attempting to clean up the
previous connections/consumers/producers.
Client unable to reconnect to JBoss 1.0.1.SP4 after restart
-----------------------------------------------------------
Key: JBMESSAGING-886
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-886
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Client Manager
Affects Versions: 1.0.1.SP4
Environment: Windows XP, Java 1.4.2-b28, JBoss 4.0.4.GA, Pentium 4 2GB
Reporter: Ben Anderson
Assigned To: Ovidiu Feodorov
Fix For: 1.0.1.SP5
Attachments: ReconnectTest.java
When JBoss is shutdown our producer/consumer threads appear to become 'stuck' in
the jboss client when attempting to tidy-up after the problem with the Connection is
detected. By tidy-up I mean we attempt to close our producers/consumers, sessions and
finally the connections themselves - before starting over and recreating everything (i.e.
the connection, session etc).
Restarting the server again will often 'unlock' the producer/consumer threads
This issue may be a dupe of http://jira.jboss.com/jira/browse/JBMESSAGING-836
--
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