[
https://issues.apache.org/jira/browse/SLING-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195181#comment-13195181
]
Rohit Nijhawan commented on SLING-2384:
---------------------------------------
>From sling launchpad standalone here's what worked for oracle.
Assume that launchpad is run for the first time and there are no browsers
already on it
1. Install the oracle jdbc bundle (osgi, not just driver) with the start option
checkbox.
2. shut down the embedded repository bundle (click stop)
3. You have to modify 3 files - jackrabbit/repository.xml, and the
workspace.xml under workspace/sdefault and workspaces/security
4. Point to the database in PersistenceManager, FileSystem and Datastore tags
everwhere applicable
5. Clean the database of any previous jcr tables
6. Restart the embedded repository.
7. Remove the deby bundle
8. Test with some content upload
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
