/, Installations/Setting up Derby for the Interwoven Event SubSystem

Problem

You are trying to setup Derby database for use with the Interwoven Event SubSystem.

You have followed the installation instructions manual

You get the following error in the eventsubd.log when starting the Event Subsytem:
“Cannot create PoolableConnectionFactory”.

Potential Solution

Check where the testdb database file has been created as the default in the Interwoven instructions creates the db file in your current working directory. Derby looks for the database by default in it derby/bin

Other possible problems:

1. Check the database exists by connecting to it and doing a “show tables” as per the Interwoven instructions
2. Check the driver exists and is in the correct location (/usr/iw-home/eventsubsystem/lib/derbyclient.jar – is “374965” in size for TS 6.7.1)

3. Check your configuration in “/usr/iw-home/eventsubsystem/conf/jmsconfignew.xml”

Should be as follows:

<DatabaseConfiguration>
<RdbmsDatabaseConfiguration
driver=”org.apache.derby.jdbc.ClientDriver”
url=”jdbc:derby://localhost:1527/testdb”
user=”usr”
maxActive=”10″
maxIdle=”5″
minIdleTime=”1800″
evictionInterval=”3600″ />
</DatabaseConfiguration>
ERROR

EVENTSUBD_HOME is set to /usr/iw-home/eventsubsystem
OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory, cause:

java.sql.SQLException: The connection was refused because the database testdb was not found.
at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection
(DriverConnectionFactory.java:82)

Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused because the database testdb was not found.

By |2009-01-10T04:52:19+00:00January 10th, 2009|Common Errors, Installations|0 Comments

About the Author: