jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2889) Occasional JCA test failures
Date Thu, 17 Feb 2011 16:04:24 GMT

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

Jukka Zitting updated JCR-2889:

    Fix Version/s:     (was: 2.3.0)

Merged to the 2.2 branch in revision 1071668 and to the 2.1 branch in revision 1071669.

> Occasional JCA test failures
> ----------------------------
>                 Key: JCR-2889
>                 URL: https://issues.apache.org/jira/browse/JCR-2889
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, jackrabbit-jca
>    Affects Versions: 2.2.4
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.1.4, 2.2.5
> As discussed in JCR-2870, the JCA packaging tests are occasionally failing with assertion
failures in TransientRepository.startRepository(). We haven't seen this before JCR-2870, but
it doesn't look like that change could possibly trigger this failure except perhaps by subtly
affecting garbage collection. Thus I'm opening this new issue to track this as a separate
> Based on my analysis so far it looks likely that this problem has something to do with
the ReferenceMap used by TransientRepository to track open sessions. The fact that the problem
occurs only occasionally and on just some systems supports the assumption that this is related
to some non-deterministic process like garbage collection.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message