camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Resolved: (CAMEL-961) Reporting exceptions back to the jms requester in in-out exchange style
Date Thu, 02 Apr 2009 05:15:34 GMT


Claus Ibsen resolved CAMEL-961.

       Resolution: Fixed
    Fix Version/s: 2.0.0

In Camel 2.0 you can enable transferring exceptions over JMS with the *transferException*

> Reporting exceptions back to the jms requester in in-out exchange style
> -----------------------------------------------------------------------
>                 Key: CAMEL-961
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 1.4.0
>            Reporter: Markus Wolf
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.0.0
>         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.

View raw message