jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Köll (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2207) XATest error: commit from different thread but same XID must not block
Date Thu, 17 Sep 2009 09:02:58 GMT

    [ https://issues.apache.org/jira/browse/JCR-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756428#action_12756428
] 

Claus Köll commented on JCR-2207:
---------------------------------

Hi Jukka i found that your change will never throw the SystemException. I have changed the
code in the DefaultISMLocking
so that the Exception should occure but it doesn't, the Testcase works always.


> XATest error: commit from different thread but same XID must not block
> ----------------------------------------------------------------------
>
>                 Key: JCR-2207
>                 URL: https://issues.apache.org/jira/browse/JCR-2207
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> I'm seeing the following test error quite often in the CI server at work:
> testDistributedThreadAccess(org.apache.jackrabbit.core.XATest)  Time elapsed: 0.213 sec
 <<< ERROR!
> javax.transaction.SystemException: commit from different thread but same XID must not
block
> 	at org.apache.jackrabbit.core.UserTransactionImpl.commit(UserTransactionImpl.java:147)
> 	at org.apache.jackrabbit.core.XATest.testDistributedThreadAccess(XATest.java:1637)
> It seems to be a system-specific issue, as I've never seen the same error locally or
on Hudson.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message