Camel Error handling throwing exception; not moving to error queue

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
This post was updated on .
Trying to test error handling scenario. ON PURPOSE I am passing in a wrong JNDI name (Webshpere MQ setup) when receipientList is publishing messages to those queues.

Following deadLetterChannel is configured for the route.
errorHandler(deadLetterChannel(qName).useOriginalMessage())

During following exception it's not able to move message to the errorQueue. How can this be handled to forward to the error queue?

org.apache.camel.processor.UnitOfWorkProcessor - Caught unhandled exception while processing ExchangeId: ID-xxxxx
org.springframework.jms.support.destination.DestinationResolutionException: Destination [BOGUS] not found in JNDI; nested exception is javax.naming.NameNotFoundException: BOGUS
        at org.springframework.jms.support.destination.JndiDestinationResolver.resolveDestinationName(JndiDestinationResolver.java:122)
        at org.springframework.jms.support.destination.JmsDestinationAccessor.resolveDestinationName(JmsDestinationAccessor.java:100)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.access$200(JmsConfiguration.java:155)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate$3.doInJms(JmsConfiguration.java:188)
        at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:186)
        at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:359)
        at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:313)
        at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:111)
        at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
        at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:333)
        at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:223)
        at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150)
        at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117)
        at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)
        at org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:709)
        at org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:80)
        at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:296)
        at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:281)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.NameNotFoundException: BOGUS
        at com.sun.jndi.fscontext.RefFSContext.getObjectFromBindings(RefFSContext.java:400)
        at com.sun.jndi.fscontext.RefFSContext.lookupObject(RefFSContext.java:327)
        at com.sun.jndi.fscontext.RefFSContext.lookup(RefFSContext.java:146)
        at com.sun.jndi.fscontext.FSContext.lookup(FSContext.java:127)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154)
        at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87)
        at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152)
        at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
        at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95)
        at org.springframework.jms.support.destination.JndiDestinationResolver.resolveDestinationName(JndiDestinationResolver.java:111)
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
My response was prematured. Apparently I still get followign exception. now standing up against a wall. Anybody any idea? unable to handle it/catch/unable to forward to error queue.

2012-06-07 17:12:19.931 [pool-12-thread-13] [WARN ] org.apache.camel.processor.UnitOfWorkProcessor - Caught unhandled exception while processing ExchangeId: ID-xxxxorg.springframework.jms.support.destination.DestinationResolutionException: Destination [BOGUS] not found in JNDI; nested exception is javax.naming.NameNotFoundException: BOGUS
        at org.springframework.jms.support.destination.JndiDestinationResolver.resolveDestinationName(JndiDestinationResolver.java:122)
        at org.springframework.jms.support.destination.JmsDestinationAccessor.resolveDestinationName(JmsDestinationAccessor.java:100)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.access$200(JmsConfiguration.java:155)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate$3.doInJms(JmsConfiguration.java:188)
        at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
        at org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate.send(JmsConfiguration.java:186)
        at org.apache.camel.component.jms.JmsProducer.doSend(JmsProducer.java:359)
        at org.apache.camel.component.jms.JmsProducer.processInOnly(JmsProducer.java:313)
        at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:111)
        at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
        at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:333)
        at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:223)
        at org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150)
        at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117)
        at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:99)
        at org.apache.camel.processor.MulticastProcessor.doProcessParallel(MulticastProcessor.java:709)
        at org.apache.camel.processor.MulticastProcessor.access$200(MulticastProcessor.java:80)
        at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:296)
        at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:281)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: javax.naming.NameNotFoundException: BOGUS
        at com.sun.jndi.fscontext.RefFSContext.getObjectFromBindings(RefFSContext.java:400)
        at com.sun.jndi.fscontext.RefFSContext.lookupObject(RefFSContext.java:327)
        at com.sun.jndi.fscontext.RefFSContext.lookup(RefFSContext.java:146)
        at com.sun.jndi.fscontext.FSContext.lookup(FSContext.java:127)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154)
        at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87)
        at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152)
        at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
        at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95)
        at org.springframework.jms.support.destination.JndiDestinationResolver.resolveDestinationName(JndiDestinationResolver.java:111)  

Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
Anyone?
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

Claus Ibsen-2
What version of Camel are you using?



On Fri, Jun 8, 2012 at 6:46 PM, javaxmlsoapdev <[hidden email]>wrote:

> Anyone?
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714225.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



--
Claus Ibsen
-----------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
using 2.9.2. Could you let me know if there is an issue with such deadLetterChannel setting working with receipientList EIP?

Thanks,
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

Claus Ibsen-2
Hi

What's the route you use? You have a recipient list somewhere. How have you
configured this?


On Mon, Jun 11, 2012 at 3:15 PM, javaxmlsoapdev <[hidden email]>wrote:

> using 2.9.2. Could you let me know if there is an issue with such
> deadLetterChannel setting working with receipientList EIP?
>
> Thanks,
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714290.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



--
Claus Ibsen
-----------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

Claus Ibsen-2
Hi

I found a bug and logged a ticket
https://issues.apache.org/jira/browse/CAMEL-5363



On Tue, Jun 12, 2012 at 3:04 PM, Claus Ibsen <[hidden email]> wrote:

> Hi
>
> What's the route you use? You have a recipient list somewhere. How have
> you configured this?
>
>
> On Mon, Jun 11, 2012 at 3:15 PM, javaxmlsoapdev <[hidden email]>wrote:
>
>> using 2.9.2. Could you let me know if there is an issue with such
>> deadLetterChannel setting working with receipientList EIP?
>>
>> Thanks,
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-Error-handling-throwing-exception-not-moving-to-error-queue-tp5714076p5714290.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>



--
Claus Ibsen
-----------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Reply | Threaded
Open this post in threaded view
|

Re: Camel Error handling throwing exception; not moving to error queue

javaxmlsoapdev
Thanks Claus