[
https://issues.apache.org/jira/browse/AMQ-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5189.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.10.0
Assignee: Timothy Bish
Nice idea, patch looks good, applied to trunk.
> Rollback on XASession when closing back to pool
> -----------------------------------------------
>
> Key: AMQ-5189
> URL: https://issues.apache.org/jira/browse/AMQ-5189
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-pool
> Affects Versions: 5.7.0, 5.8.0, 5.9.0, 5.9.1
> Environment: Windows, UNIX
> Reporter: Benjamin Graf
> Assignee: Timothy Bish
> Fix For: 5.10.0
>
> Attachments: vcs-diff962688386413870521.patch
>
>
> If you have a pool of XASession under load (heavy load might be necessary) I
> register sometimes following Exception "Cannot rollback() inside an
> XASession" in afterCompletion synchronisation. After some analysis and
> patching with logging I recognized that the session object is returned back
> to pool before setting the xa flag back to false. This leads to the effect
> that this session gets be used again by another thread while the earlier one
> switches the xa flag to false.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
