[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-5189) Rollback on XASession when closing back to pool
From:       "Benjamin Graf (JIRA)" <jira () apache ! org>
Date:       2014-05-29 7:28:02
Message-ID: JIRA.12714812.1400260815408.37471.1401348482043 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQ-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012155#comment-14012155 \
] 

Benjamin Graf commented on AMQ-5189:
------------------------------------

Patch suggestion

> 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
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]