[
https://issues.apache.org/jira/browse/JCR-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715886#comment-15715886
]
ASF GitHub Bot commented on JCR-4073:
-------------------------------------
GitHub user woonsan opened a pull request:
https://github.com/apache/jackrabbit/pull/48
JCR-4073: wait until the purgin thread completes.
Just happened to see this ticket. I guess it was caused by the fact that
the purging is done in an asynchronous thread and occasionally there might have
been a timing issue as Amit already pointed out in the ticket.
Perhaps my pull request will fix this problem.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/woonsan/jackrabbit bugfix/JCR-4073
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jackrabbit/pull/48.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #48
----
commit d73b7645e27179ec7b6732f20558c25380a35407
Author: Woonsan Ko <[email protected]>
Date: 2016-12-02T18:27:07Z
JCR-4073: wait until the purgin thread completes.
----
> jackrabbit-data: occasional test failures in TestLocalCache.testAutoPurge
> -------------------------------------------------------------------------
>
> Key: JCR-4073
> URL: https://issues.apache.org/jira/browse/JCR-4073
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-data
> Reporter: Julian Reschke
> Assignee: Amit Jain
>
> {noformat}
> Error Message
> a1 should be null
> Stacktrace
> junit.framework.AssertionFailedError: a1 should be null
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNull(Assert.java:237)
> at
> org.apache.jackrabbit.core.data.TestLocalCache.testAutoPurge(TestLocalCache.java:197)
> {noformat}
> Maybe caused by JCR-4007?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
