Hi,

I'm running Camel version 2.24.0, I saw the same issue with 2.23.x.

I've got a route that connects two JMS systems. The Producer is configured with 
a dynamic to:

<c:from uri="tibco:topic:PAR.*.FX.DATA.>"/>
<c:toD 
uri="solace-jms:topic:${header.jmsDestination.topicName.replace('.','/')}" />

Sometimes, but not always, we get this error on startup:

java.util.concurrent.RejectedExecutionException: null
    at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:144) 
~[camel-jms-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:178)
 ~[camel-core-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445) 
~[camel-core-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:160)
 ~[camel-core-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
 [camel-core-2.23.1.jar!/:2.23.1]    at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
 [camel-core-2.23.1.jar!/:2.23.1]    at 
org.apache.camel.processor.Pipeline.process(Pipeline.java:138) 
[camel-core-2.23.1.jar!/:2.23.1]
    at org.apache.camel.processor.Pipeline.process(Pipeline.java:101) 
[camel-core-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
 [camel-core-2.23.1.jar!/:2.23.1]    at 
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
 [camel-core-2.23.1.jar!/:2.23.1]
    at 
org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:113)
 [camel-jms-2.23.1.jar!/:2.23.1]

This seems to happen when messages are coming in before the producer is fully 
initialized. If I wait until Camel starts before I start the message flow, 
everything works fine.

I'm not the only one to see this problem. Someone else reported the same thing, 
the stack trace is almost identical (line numbers are a bit different because 
it's a different version:

https://github.com/camelinaction/camelinaction2/issues/18

Has anyone else seen this? Does anyone know how to fix it?

Thanks
Michael Davis
Ottawa

Reply via email to