camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [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
Date Thu, 20 Nov 2008 04:58:05 GMT

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

Willem Jiang updated CAMEL-959:
-------------------------------

        Fix Version/s: 1.5.1
    Affects Version/s: 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
>    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.


Mime
View raw message