jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Perepelytsya (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1354) Repository shutdown reposts ERROR: failed to close connection
Date Tue, 05 Aug 2008 21:22:44 GMT

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

Andrew Perepelytsya updated JCR-1354:
-------------------------------------

    Attachment: derby.log

Hi, after enabling those got the attached derby.log. Not that there was an immediate cause
available, though...

In my case got this error by simply shutting the just started app with an embedded jackrabbit,
no changes made after start. The error, however, only exhibits itself if the *bundle* persistence
managers are used, the standard 'db' ones don't have the error. But, the whole idea of using
bundle PMs was to leverage the new DataStore facility (not really useful with plain db PMs).

Here's the app shutdown log:

[08-05 17:20:06] INFO  / [Shutdown]: Closing Spring root WebApplicationContext
[08-05 17:20:07] ERROR ConnectionRecoveryManager [Shutdown]: failed to close connection, reason:
No current connection., state/code: 08003/40000
[08-05 17:20:07] WARN  DbFileSystem [Shutdown]: execute failed, about to reconnect...
[08-05 17:20:17] ERROR RepositoryImpl [Shutdown]: Error while closing Version Manager.
java.sql.SQLException: No current connection.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedConnection.getMetaData(Unknown Source)
	at org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager.close(DerbyPersistenceManager.java:318)
	at org.apache.jackrabbit.core.version.VersionManagerImpl.close(VersionManagerImpl.java:201)
	at org.apache.jackrabbit.core.RepositoryImpl.doShutdown(RepositoryImpl.java:1000)
	at org.apache.jackrabbit.core.RepositoryImpl.shutdown(RepositoryImpl.java:948)
	at org.springmodules.jcr.jackrabbit.RepositoryFactoryBean.destroy(RepositoryFactoryBean.java:91)
	at org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:154)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:397)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:375)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:348)
	at org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:861)
	at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:839)
	at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:802)
	at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:367)
	at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:70)
	at org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:573)
	at org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:484)
	at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65)
	at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:129)
	at org.mortbay.jetty.Server.doStop(Server.java:281)
	at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65)
	at org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:559)
[08-05 17:20:17] WARN  DbFileSystem [Shutdown]: execute failed, about to reconnect...
[08-05 17:20:27] INFO  log [Shutdown]: Shutdown hook complete

Process finished with exit code 1


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


Mime
View raw message