My organization has had a hard time dealing with some stubborn JMS issues. We have several JBoss instances running on a network, and occassionally have to restart JBoss instances that are acting as JMS clients (using durable subscriptions). The problem is that the clients are not disconnecting properly, so when they try to connect, we get a message saying that they are already subscribed.

This usually means that we have to stop the JBoss instance that is running as the JMS server, and clear out database tables used for JMS. Then we can restart the server, and the clients can connect to it again.

Has anyone run into this problem? Any suggestions?

Thanks in advance.

link|improve this question
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.