You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2008/02/25 09:14:51 UTC
[jira] Created: (JCR-1414) Data store garbage collection: inUse not
correctly synchronized
Data store garbage collection: inUse not correctly synchronized
---------------------------------------------------------------
Key: JCR-1414
URL: https://issues.apache.org/jira/browse/JCR-1414
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: core 1.4.1, 1.4
Reporter: Thomas Mueller
Assignee: Thomas Mueller
Fix For: core 1.4.2
Access to the fields DbDataStore.inUse and FileDataStore.inUse is not synchronized.
This is a problem when concurrently calling GarbageCollector.deleteUnused()
and accessing the data store (ConcurrentModificationException is thrown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1414) Data store garbage collection: inUse
not correctly synchronized
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575341#action_12575341 ]
Jukka Zitting commented on JCR-1414:
------------------------------------
Does the above commit resolve this issue? I merged it to the 1.4 branch in revision 633844.
> Data store garbage collection: inUse not correctly synchronized
> ---------------------------------------------------------------
>
> Key: JCR-1414
> URL: https://issues.apache.org/jira/browse/JCR-1414
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: core 1.4.2
>
>
> Access to the fields DbDataStore.inUse and FileDataStore.inUse is not synchronized.
> This is a problem when concurrently calling GarbageCollector.deleteUnused()
> and accessing the data store (ConcurrentModificationException is thrown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1414) Data store garbage collection: inUse
not correctly synchronized
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved JCR-1414.
---------------------------------
Resolution: Fixed
Yes, the commit resolves the problem.
> Data store garbage collection: inUse not correctly synchronized
> ---------------------------------------------------------------
>
> Key: JCR-1414
> URL: https://issues.apache.org/jira/browse/JCR-1414
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: core 1.4.2
>
>
> Access to the fields DbDataStore.inUse and FileDataStore.inUse is not synchronized.
> This is a problem when concurrently calling GarbageCollector.deleteUnused()
> and accessing the data store (ConcurrentModificationException is thrown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1414) Data store garbage collection: inUse
not correctly synchronized
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573204#action_12573204 ]
Thomas Mueller commented on JCR-1414:
-------------------------------------
Committed in revision 631905.
This is quite a large patch, sorry! To test it, first configure the data store in the src/test/repository/repository.xml (for example: <DataStore class="org.apache.jackrabbit.core.data.FileDataStore"></DataStore>), and then run the test case org.apache.jackrabbit.core.data.GCConcurrentTest with the system property jackrabbit.test.scale set to 100 or larger. By default this test case is very quick and will not find the problem.
> Data store garbage collection: inUse not correctly synchronized
> ---------------------------------------------------------------
>
> Key: JCR-1414
> URL: https://issues.apache.org/jira/browse/JCR-1414
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: core 1.4.2
>
>
> Access to the fields DbDataStore.inUse and FileDataStore.inUse is not synchronized.
> This is a problem when concurrently calling GarbageCollector.deleteUnused()
> and accessing the data store (ConcurrentModificationException is thrown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1414) Data store garbage collection: inUse
not correctly synchronized
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834241#action_12834241 ]
Thomas Mueller commented on JCR-1414:
-------------------------------------
Revision 633844 also fixed a bug in BundleDbPersistenceManager, which caused data store garbage collection
to delete almost all data when using a BundleDbPersistenceManager. See also JCR-2492.
> Data store garbage collection: inUse not correctly synchronized
> ---------------------------------------------------------------
>
> Key: JCR-1414
> URL: https://issues.apache.org/jira/browse/JCR-1414
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: core 1.4.2
>
>
> Access to the fields DbDataStore.inUse and FileDataStore.inUse is not synchronized.
> This is a problem when concurrently calling GarbageCollector.deleteUnused()
> and accessing the data store (ConcurrentModificationException is thrown).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.