This content has been marked as final.
Show 3 replies
-
1. Re: Restarting JMS
stephanenicoll May 20, 2004 8:18 AM (in response to richieb)Why not searching the origin of the deadlock in a first place?
Regards,
Stephane -
2. Re: Restarting JMS
richieb May 20, 2004 8:53 AM (in response to richieb)"StephaneNicoll" wrote:
Why not searching the origin of the deadlock in a first place?
I am looking into it.
But this is a production system that needs to be up all the time. Restarting JBoss is bit drastic, as it kicks all users off and makes our app UI unavailable for a while.
Restarting JMS only would be cleaner way to work around this problem until I get a handle on why it occurs.
...richie -
3. Re: Restarting JMS
adrian.brock May 20, 2004 9:39 AM (in response to richieb)If you have 3.2.3, you can touch your jms persistence manager -service.xml
which will redeploy the whole of jms (everything depends upon the persistence manager
either directly or indirectly).
But, if clients are connected you will get an error message saying the destinations
are in use and it won't work. This has been fixed for jboss-3.2.4, the clients
are thrown off.