Hi
You need to quote the class name, eg
${body} is 'au.edu.mq.ClassA'
On Mon, Apr 28, 2014 at 8:21 AM, damien wrote:
> Hi,
>
> The predict works fine in camel 2.8:
>
>
>
> ${body} is
> au.edu.mq
Hi
We are running a lot of Camel routes on Weblogic. The only time I have seen
stuck threads in on the commons.net.ftp, and the uses here is not related to
any Camel component.
"[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default
(self-tuning)'" - Thread t@65134
java.lang.Thread.St
Hi,
The predict works fine in camel 2.8:
${body} is
au.edu.mq.ClassA
But when I upgrade to camel 2
I'm not sure if the following is a bug that needs to be reported, and that
I'm missing something obvious.
For a single route with multiple JMS queues, the first queue is properly
dequeued, but the remaining routes do not have the ActiveMQ message
dequeued.
a. Messages flow through the system to c