[
https://issues.apache.org/activemq/browse/CAMEL-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47574#action_47574
]
Claus Ibsen commented on CAMEL-959:
-----------------------------------
Remember to update the wiki at:
http://activemq.apache.org/camel/jms.html
At least update
- add it as an option in the big list
- consider adding a h3. section about using transactedInOut to explain what
it's used for. Maybe James can help with a good description and sample.
Willem see this patch for trunk, maybe it should be in 1.5.1 since this ticket
is also target for 1.5.1
http://svn.apache.org/viewvc/activemq/camel/trunk/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsConfiguration.java?rev=719851&r1=719850&r2=719851&view=diff
> 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.
