Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <2119266962.1223615872686.JavaMail.jira@brutus>
Date: Thu, 9 Oct 2008 22:17:52 -0700 (PDT)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Issue Comment Edited: (CAMEL-961) Reporting exceptions back
 to the jms requester in in-out exchange style
In-Reply-To: <1633714424.1223281912590.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

hadrian edited comment on CAMEL-961 at 10/9/08 10:16 PM:
-----------------------------------------------------------------

Can we close this one with a "won't fix"?

@Markus, I think CAMEL-960 will solve your problem.

      was (Author: hadrian):
    Can we close this one with a "won't fix"?
  
> 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.