You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/07/12 01:41:14 UTC

[jira] Resolved: (JCR-2207) XATest error: commit from different thread but same XID must not block

     [ https://issues.apache.org/jira/browse/JCR-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-2207.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

I increased the block detection timeout from 0.2 seconds to 1.0 seconds in revision 793240. This seems to have helped, so I'm resolving this as Fixed.

> 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: 2.0.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.