[jira] Updated: (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

["Hadrian Zbarcea (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea updated CAMEL-959:
----------------------------------

    Fix Version/s: 2.0.0
                       (was: 1.5.0)

> 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
>            Reporter: James Strachan
>             Fix For: 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.