[
https://issues.apache.org/jira/browse/JCR-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626422#comment-13626422
]
Marcel Reutegger commented on JCR-3547:
---------------------------------------
bq. AbstractJCRTest#setup do initialize new repository for each test case
No, that's not the case. Tests extending from AbstractJCRTest may share a
repository instance in a way that one test triggers the startup of the
repository an another tests re-uses the already initialized repository.
AbstractJCRTest will make sure no two tests run concurrently on a given
repository instance. The purpose of setUp() and tearDown() in AbstractJCRTest
to perform cleanup and initialization of *content* in the repository, but not
the repository itself. This was done to minimize initialization overhead.
> Datastore GC doesn't reset updateModifiedDateOnAccess on datastore
> ------------------------------------------------------------------
>
> Key: JCR-3547
> URL: https://issues.apache.org/jira/browse/JCR-3547
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4, 2.5
> Reporter: Shashank Gupta
> Attachments: GarbageCollector.java.patch,
> GC_prevent_concurrent_run_app2.patch, GC_prevent_concurrnet_run_app1.patch
>
>
> In mark phase, GC updates store.updateModifiedDateOnAccess with current time,
> so that datastore updates record’s lastModified timestamp upon subsequent
> read/scan.
> But GC doesn't reset it to 0. So even after GC completes, datastore will
> continue updating lastModified timestamp on read invocations and it will have
> performance impact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
