[
https://issues.apache.org/jira/browse/AMQ-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated AMQ-5031:
---------------------------------
Fix Version/s: 5.9.1
> Allow isSameRM override from broker identity to connection identity to avoid
> xa.join
> ------------------------------------------------------------------------------------
>
> Key: AMQ-5031
> URL: https://issues.apache.org/jira/browse/AMQ-5031
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMS client
> Affects Versions: 5.9.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Labels: 2pc, isSameRm, join, xa
> Fix For: 5.9.1, 5.10.0
>
>
> When two connection are involved in an xa transaction, 1pc is great and
> basing the xaresource identity on the broker identity makes sense. However in
> the cases that an joined xa association is not ended, which seems ok from an
> xa perspective, a joined association is left in error.
> To avoid this, we need a way to force 2pc across multiple connections to the
> same broker.
> A broker url param like jms.rmIdFromConnectionId=true will do the trick and
> ensure that the RM identity is tied to the connection and not the broker.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
