jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1354) Repository shutdown reposts ERROR: failed to close connection
Date Sat, 16 Feb 2008 14:41:08 GMT

     [ https://issues.apache.org/jira/browse/JCR-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1354:
-------------------------------

    Fix Version/s:     (was: 1.4.1)

Derby fails with "No current connection" if some previous operation has failed for some reason.

Can you set the following in a derby.properties file and see if any errors are logged:

    derby.stream.error.logSeverityLevel=0
    derby.language.logStatementText=true 


> 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
>   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.


Mime
View raw message