http://issues.apache.org/activemq/browse/CAMEL-1751
Disregard this section. It was a double paste ..
> class="com.inwk.jobtemplate.server.ReturnedQueueRouteBuilder"
> lazy-init="false" init-method="init" destroy-method="stop">
>
>
>
> class="com.inwk.jobtemplate.server.ReturnedQuotesProce
On Tue, Jun 23, 2009 at 8:34 AM, David Durham wrote:
> On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully 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
On Tue, Jun 23, 2009 at 4:35 AM, Gary Tully 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 'useShutdownHook'
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 confi
>> 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 CamelCon
On Mon, Jun 22, 2009 at 2:40 PM, David Durham 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 for it? I've trie
