[jboss-jira] [JBoss JIRA] (JBAS-6348) Problem with QueuedPessimisticEJBLock and Arjuna

[Junhui Luo (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12825345#comment-12825345 ] 

Junhui Luo commented on JBAS-6348:
----------------------------------

Is a fix for this bug available for JBoss community edition 4.2.3 GA or must I migrate to JBoss 6.0 or above to get the fix?
                
> Problem with QueuedPessimisticEJBLock and Arjuna
> ------------------------------------------------
>
>                 Key: JBAS-6348
>                 URL: https://issues.jboss.org/browse/JBAS-6348
>             Project: Application Server 3  4  5 and 6
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager Integration (Arjuna)
>    Affects Versions: JBossAS-4.2.3.GA
>            Reporter: husgaard
>            Assignee: Alexey Loubyansky
>             Fix For: 6.0.0.Final
>
>
> When using Arjuna, QueuedPessimisticEJBLock does not always properly detect that a waiting tx has timed out. The problem is that QueuedPessimisticEJBLock was written for the old TM, which did not rollback transactions on timeout, but only marked them for rollback. Now that Arjuna is in play, it has to check for rolled back transactions too.
> The isTxExpired() method should be changed to something like this:
> protected boolean isTxExpired(Transaction miTx) throws Exception {
> 	if (miTx != null
> 			&& (miTx.getStatus() == Status.STATUS_MARKED_ROLLBACK || miTx.getStatus() == Status.STATUS_ROLLEDBACK)) {
> 		return true;
> 	}
> 	return false;
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira