[
http://jira.jboss.com/jira/browse/JBMESSAGING-965?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-965:
-------------------------------------
You need to post the usual stuff:
Your stack trace, the version of JBM you're using, the version of JBAS you're
using, version of JVM etc
JBoss Messaging client fails to reconnect after restart of the
server
---------------------------------------------------------------------
Key: JBMESSAGING-965
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-965
Project: JBoss Messaging
Issue Type: Bug
Reporter: pgervais
Assigned To: Tim Fox
There seem to be a clean up problem with the client JBoss Messaging QueueConnection.
When following these steps, everything works fine:
1. create a QueueConnection
2. create a QueueSender
3. send a message
4. create QueueReceiver (on the same queue as the QueueSender)
5. receive the sent message
6. close the connection
7. shutdown the JBoss server
8. restart the JBoss server
9. execute step 1-6
Everything works fine
But following these steps:
1. create a QueueConnection
2. create a QueueSender
3. send a message
4. create QueueReceiver (on the same queue as the QueueSender)
5. receive the sent message
6. shutdown the JBoss server
7. close the connection (I get an exception, it should be normal)
8. restart the JBoss server
9. execute step 1, I get an exception, this should not be normal
After investigating, I think that the problem happens when the close is executed in the
second case. It seems that an exception is thrown before all the clean up has been done,
because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine
address and what seems to be the port on which the thread is listening). That thread was
not present in the first case, it disappeared after executing close on the
QueueConnection.
After further investigation, it seems that the problem is due to a clean up problem with
the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the
previously created connection are not unregistered when the close method fails.
--
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