Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <605614322.1229926385496.JavaMail.jira@brutus>
Date: Sun, 21 Dec 2008 22:13:05 -0800 (PST)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-959) JMS InOut operations should default
 to non transacted even if the JMS component or endpoint defaults to
 transacted; as typically RPCs over JMS are not transacted
In-Reply-To: <2120518142.1222964812588.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-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48297#action_48297 ] 

Willem Jiang commented on CAMEL-959:
------------------------------------


User should avoid the situation of configure the same transaction manager for two jms component in the same route rule for the InOut message.
{code}
 from("activemq:queue:mainStage?replyTo=queue:mainStage.reply").to("activemq:queue:request?replyTo=queue:request.reply");
{code}

If not , you will get transaction time out exception, since the message sending to the second queue will never  be committed in a single local transaction.

> JMS InOut operations should default to non transacted even if the JMS component or endpoint defaults to transacted; as typically RPCs over JMS are not transacted
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-959
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-959
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 1.5.0
>            Reporter: James Strachan
>            Assignee: James Strachan
>             Fix For: 1.5.1, 2.0.0
>
>
> currently there is no automatic transaction commit inside the send of the request when doing InOut with JMS; so the transaction won't commit if the component/endpoint is transacted - then the message won't reach the request and things will time out.
> This will be confusing to users.
> So if things are transacted; lets default to using non-transacted for InOut - and force a new property, transactedInOut to allow that to be transacted if folks really want that (which they usually won't I'd have thought).

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