You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Ian Boston (JIRA)" <ji...@apache.org> on 2013/02/15 09:19:12 UTC
[jira] [Resolved] (SLING-2384) Can't remove Derby from running
instance of launchpad
[ https://issues.apache.org/jira/browse/SLING-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston resolved SLING-2384.
-------------------------------
Resolution: Not A Problem
The correct procedure was given in the previous comment, and hence documented.
> Can't remove Derby from running instance of launchpad
> -----------------------------------------------------
>
> Key: SLING-2384
> URL: https://issues.apache.org/jira/browse/SLING-2384
> Project: Sling
> Issue Type: Bug
> Components: Documentation
> Environment: windows 7, java 1.6.0_29
> Reporter: Rohit Nijhawan
>
> In the steps given to change jackrabbit persistence outlined here
> http://sling.apache.org/site/jackrabbit-persistence.html
> The first step asking you to uninstall the Derby Bundle causes the whole thing collapse. How then can one use these steps to add another database?
> Here's what the log file showed
> 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent STOPPED
> 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNRESOLVED
> 25.01.2012 16:31:12.198 *INFO* [FelixDispatchQueue] derby BundleEvent UNINSTALLED
> 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent INSTALLED
> 25.01.2012 16:31:38.297 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent RESOLVED
> 25.01.2012 16:31:38.312 *INFO* [FelixDispatchQueue] ojdbc14 BundleEvent STARTED
> <snip>
> 1. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager execute failed, about to reconnect...
> 1a. org.apache.sling.jcr.jackrabbit.server stopRepository: Uncaught problem unregistering the repository service (java.lang.IllegalStateException: Service already unregistered.) java.lang.IllegalStateException: Service already unregistered.
> at org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:125)
> at org.apache.sling.jcr.base.AbstractSlingRepository.unregisterService(AbstractSlingRepository.java:536)
> at org.apache.sling.jcr.base.AbstractSlingRepository.stopRepository(AbstractSlingRepository.java:861)
> at org.apache.sling.jcr.base.AbstractSlingRepository.deactivate(AbstractSlingRepository.java:638)
> 2. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to re-establish connection java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager
> at org.apache.derby.jdbc.AutoloadedDriver.getDriverModule(Unknown Source)
> at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
> at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
> at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
> 3. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to check existence of node state: fbc3862a-ff93-e87f-7b11-4d9b674580fa java.sql.SQLNonTransientConnectionException: No current connection.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.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)
> 3a. org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager failed to re-establish connection java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager
> I took out the exception stack but this is the order in which they came.
--
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