[
https://issues.apache.org/jira/browse/AMQ-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5264.
-----------------------------
Resolution: Fixed
Assignee: Gary Tully
added configuration attribute useSessionArgs in
http://git-wip-us.apache.org/repos/asf/activemq/commit/9e139017
when true, a call to createSession(true,...) will allow session.commit as
normal. When false, the args to create session for a managed connection factory
created connection (managed connection) are ignored because the expectation is
that the container will do transaction demarcation via the xa or rar local
transaction contracts.
example of usage:
https://github.com/gtully/activemq-arquillian/blob/master/javaee/mdb-tx-send-two/server/standalone/configuration/standalone-example.xml#L372
> Allow optional manual transaction management on a rar managedConnection
> ------------------------------------------------------------------------
>
> Key: AMQ-5264
> URL: https://issues.apache.org/jira/browse/AMQ-5264
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JCA Container
> Affects Versions: 5.10.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: jca, jms, jms-compliance
> Fix For: 5.11.0
>
>
> In
> https://github.com/apache/activemq/commit/adb49f562725087865ded9a773ee6901423c870b
> the jee semantics were tightened up to ignore args passed to create session.
> see:
> http://mail-archives.apache.org/mod_mbox/activemq-users/201407.mbox/%3CCAH%2BvQmPgMYGmWB_QX8gcFqMOcFa9mGkZEDjhEiASpbUKen3f4w%40mail.gmail.com%3E
> In cases where spring is uses with the rar outside of ee, it is sensible to
> retain the standard jms semantics and respect that args. The app is then
> responsible for ensuring transaction completion as normal.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
