http://issues.apache.org/activemq/browse/CAMEL-1751
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
On Tue, Jun 23, 2009 at 4:35 AM, Gary Tullygary.tu...@gmail.com wrote:
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
On Tue, Jun 23, 2009 at 8:34 AM, David Durhamdavid.durham...@gmail.com wrote:
On Tue, Jun 23, 2009 at 4:35 AM, Gary Tullygary.tu...@gmail.com wrote:
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
Disregard this section. It was a double paste ..
bean id=returnQueues
class=com.inwk.jobtemplate.server.ReturnedQueueRouteBuilder
lazy-init=false init-method=init destroy-method=stop
property name=routes
map
entry
Hi all,
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,
On Mon, Jun 22, 2009 at 2:40 PM, David Durhamdavid.durham...@gmail.com wrote:
Hi all,
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
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
