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

[Vadim Kopichenko (JIRA)]

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

Vadim Kopichenko commented on JBAS-6348:
----------------------------------------

JBoss 4.2.0.GA is also affected.
Threads happen to hang with stacktrace like this:
threadState:TIMED_WAITING, lockName:org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock$TxLock at db42b8
    java.lang.Object.wait(Native Method)
    org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPessimisticEJBLock.java:323)
    org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPessimisticEJBLock.java:230)


> Problem with QueuedPessimisticEJBLock and Arjuna
> ------------------------------------------------
>
>                 Key: JBAS-6348
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6348
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager (Arjuna)
>    Affects Versions: JBossAS-4.2.3.GA
>            Reporter: Ole Husgaard
>            Assignee: Jonathan Halliday
>
> 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira