[
https://issues.apache.org/jira/browse/JCR-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-1499.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
Moved super.close() above derby 'shutdown' in DerbyPersistenceManager.
Fixed in revision: 640792
> Error logged when repository is shut down
> -----------------------------------------
>
> Key: JCR-1499
> URL: https://issues.apache.org/jira/browse/JCR-1499
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4, core 1.4.1, core 1.4.2
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.5
>
>
> This only happens with the bundle DerbyPersistenceManager.
> In DerbyPersistenceManager.close() the embedded derby database is shut down
> and then super.close() is called. There the ConnectionRecoveryManager is
> closed, which tries to operate on a connection to the already shut down derby
> database. The log contains entries like:
> 25.03.2008 13:49:29 *ERROR* [Thread-5] ConnectionRecoveryManager: failed to
> close connection, reason: No current connection., state/code: 08003/40000
> (ConnectionRecoveryManager.java, line 453)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
