Hi James attached you will find the execution log and the traces taken after the ^C As you see from the thread dump, some threads are busy doing some work (within an onMessage) but the operations they perform are guarded by a timeout that should be well expired at the moment I kill the process. Actually I don't know how this is supposed to work, but it seems that spring doesn't manage to destroy the singletons when there are active sessions.
Moreover I don't know why despite the -Dactivemq.broker.disable-clean-shutdown=true the shutdown hook still gets called, I thought the option served to disable it. In a general sense, I'm supposed to disable the hooks (for both spring and AMQ) to be able to stop the process? I had read here somewhere to do so... Thanks a lot for your help, I greatly appreciate it... http://www.nabble.com/file/6813/traces.zip traces.zip James.Strachan wrote: > > On 2/27/07, drvillo <[EMAIL PROTECTED]> wrote: >> >> Hi James >> >> I'm fine with the traces, but the problem is that they >> don't stop...there's something AMQ is still busy doing, >> and I can't figure out how to stop it. the >> Active Sessions = X >> actually decreases with time, but when that reaches 1 it >> stays like that forever (forever is ~minutes ) >> >> I'm using -Dactivemq.broker.disable-clean-shutdown=true >> but it seems not to make any difference if I remove it... >> >> >> Do you have an idea of which threads are actually still busy? > > Am not sure - any chance you could create a few stack dumps so we can > see whats going on in your environment? > >> BTW: trunk now has got rid of the messages, I guess you already >> patched the log level for these messages. > > Yeah > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Cannot-shutdown-cleanly-tf2870519s2354.html#a9180424 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
