[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

["Willem Jiang (JIRA)" <ji...@apache.org>]

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

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

For the Queue to Queue with InOut ExchangePattern , we will face another issue.
If the transacted is set to be true but the transactedInOut is false, since we don't want to use the JMS transaction,  do we still need to inject  the JMSTransacationManager for the jms MessageListenerContainer ?

Since the jms consumer doesn't know the message exchange pattern, I'd like to change current JMSConfig to take consideration of transactedInOut and transacted flags at the same time.
If they are all true, we can inject the transactionManager into the MessageListenerContainer, if any of them is false , we won't inject the transactionManger into MessageListenerContainer even the TransactionManager is configured into the JMSConfig.



> 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
>    Affects Versions: 1.5.0
>            Reporter: James Strachan
>            Assignee: Willem Jiang
>             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.