[
https://issues.apache.org/jira/browse/JCR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532496#comment-13532496
]
Nicolas Gavalda edited comment on JCR-3485 at 12/14/12 5:56 PM:
----------------------------------------------------------------
The issue can easily be reproduced, the GarbageCollectorTest.testGC unit test
fails when the following DataStore configuration is specified:
<DataStore class="org.apache.jackrabbit.core.data.db.DerbyDataStore">
<param name="url"
value="jdbc:derby:${rep.home}/repository/datastore-derby/db;create=true"/>
<param name="databaseType" value="derby"/>
<param name="driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<param name="minRecordLength" value="1024"/>
<param name="maxConnections" value="3"/>
<param name="copyWhenReading" value="true"/>
<param name="tablePrefix" value=""/>
<param name="schemaObjectPrefix" value=""/>
</DataStore>
(With the provided patch, the test still seems to fail, but the lock timeout
problems are resolved.)
was (Author: ngavalda):
The issue can easily be reproduced, the GarbageCollectorTest.testGC unit
test fails when the following DataStore configuration is specified:
{code:xml}
<DataStore class="org.apache.jackrabbit.core.data.db.DerbyDataStore">
<param name="url"
value="jdbc:derby:${rep.home}/repository/datastore-derby/db;create=true"/>
<param name="databaseType" value="derby"/>
<param name="driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<param name="minRecordLength" value="1024"/>
<param name="maxConnections" value="3"/>
<param name="copyWhenReading" value="true"/>
<param name="tablePrefix" value=""/>
<param name="schemaObjectPrefix" value=""/>
</DataStore>
{code}
(With the provided patch, the test still seems to fail, but the lock timeout
problems are resolved.)
> The Datastore garbage collector does not work with a Derby-based DbDataStore
> ----------------------------------------------------------------------------
>
> Key: JCR-3485
> URL: https://issues.apache.org/jira/browse/JCR-3485
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.4.3
> Reporter: Cédric Damioli
> Attachments: DbDataStore.patch
>
>
> We obtain a lot of Derby lock timeouts
> Looking at the code, it seems that a few ResultSets are not actually closed,
> leading to Derby keeping some locks
--
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
