You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Andrew Perepelytsya (JIRA)" <ji...@apache.org> on 2008/08/05 23:24:44 UTC
[jira] Commented: (JCR-1354) Repository shutdown reposts ERROR:
failed to close connection
[ https://issues.apache.org/jira/browse/JCR-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620049#action_12620049 ]
Andrew Perepelytsya commented on JCR-1354:
------------------------------------------
The above stacktrace is with Jackrabbit 1.4.2
> Repository shutdown reposts ERROR: failed to close connection
> -------------------------------------------------------------
>
> Key: JCR-1354
> URL: https://issues.apache.org/jira/browse/JCR-1354
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4
> Environment: Linux x86/Sun jdk 1.6.0_3
> Reporter: Alex Lukin
> Attachments: derby.log
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> Norman repository shutdow reports error twice in logs:
> ERROR: failed to close connection, reason: No current connection., state/code: 08003/40000
> ERROR: failed to close connection, reason: No current connection., state/code: 08003/40000
> Does not matter if there are not-closed sessions or not.
> Use od Derby of FS causes additional SQL exceptions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.