I wonder if this is the result of code registered with a shutdown hook and at shutdown some of the required classes are not longer available. One way to check is to have the broker not register any shutdown hook.
Set the 'useShutdownHook' property to false for the ActiveMQ broker in your xml configuration. 2009/6/22 David Durham <david.durham...@gmail.com> > >> I've got a simple ActiveMQ client running inside Tomcat. When I > >> shutdown Tomcat I get an exception from the "Inactivity Monitor Write > >> Check" thread. My question is has anyone seen this issue and have a > >> fix for it? I've tried making sure that I call the stop() method on > >> my CamelContext, but I don't see how I would call stop on the > >> Inactivity Monitor Read and Write threads. > > > > Here's a stack trace: > > > > http://pastebin.ca/1470211 > > Actually, maybe this isn't the cause of the hang. It's an assumption > on my part, because I see this error message and the server hangs. > Now I'm thinking that the Tomcat hangage could be caused by the fact > that there are still non-daemon threads running. There's a couple of > Active MQ transport threads and a couple of > DefaultMessageListenerContainer running. Anyone have experience with > using ActiveMQ/Camel and Spring under Tomcat? I'd really prefer to > not have to 'kill -9' tomcat. > > Thanks, > Dave > -- http://blog.garytully.com Open Source Integration http://fusesource.com
