[ 
https://issues.apache.org/activemq/browse/CAMEL-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46315#action_46315
 ] 

Claus Ibsen commented on CAMEL-961:
-----------------------------------

Exceptions or Exchange objects is not propagated over the JMS wire, only 
payload and primitive headers.
The JMS spec is somewhat limitied what can be sent. 

Are you using Camel on the client side as well?

If for instance the Exchange is sent over the wire as ObjectMessage then it 
requires that you have the same .class on the classpath on both the client and 
server side. And currently we do not have a eg. camel-jms-client.jar etc. or 
camel-client.jar.

What kind of response do you want to be returned when there has been a failure? 

I will check if I can find the other related tickets on this issue.


> Reporting exceptions back to the jms requester in in-out exchange style
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-961
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-961
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 1.4.0
>            Reporter: Markus Wolf
>            Assignee: Hadrian Zbarcea
>         Attachments: camel-test.tar.gz
>
>
> We tried to setup a route where some exceptions where caught by the dead 
> letter queue for retry and some exceptions where reported back to the jms 
> message requester in an in-out exchange style request.
> There are two problems with this.
> First: The dead letter queue is an all or nothing handler. There is currently 
> no way to give some excludes to the handled exceptions.
> Second: Exceptions are not serialized and returned by the jms listener on 
> reponse, but instead a camel runtime exception is logged and the jms request 
> thread gets a timeout.
> In the attached example the IOException should be returned to the 
> jms:someQueue endpoint as answer to the request. All other exceptions should 
> be handled by the dead letter queue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to