Lance J. Andersen wrote:
You never showed your config for SJSAS for your Connection Pool. Both of these allow me to ping from the gui or asadmin:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="cts-cloudscapeEmbedded-pool" pool-resize-quantity="2" res-type="javax.sql.DataSource" steady-pool-size="8">
<property name="DatabaseName" value="/tmp/DerbyDB"/>
</jdbc-connection-pool>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="derby-xa-pool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="Password" value="foo"/>
<property name="DatabaseName" value="/tmp/DerbyDB"/>
<property name="User" value="foo"/>
</jdbc-connection-pool>
Here is the resource segment (relating to derby) of the domain.xml:
<resources>
<jdbc-resource enabled="true" jndi-name="jdbc/derbyXAdb1" object-type="user" pool-name="derbyXAdb1">
<description>derby XA db1</description>
</jdbc-resource>
<jdbc-resource enabled="true" jndi-name="jdbc/derby_db1" object-type="user" pool-name="derbyDB1"/>
<jdbc-resource enabled="true" jndi-name="jdbc/DerbyDB1" object-type="user" pool-name="derbyDB1pool"/>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="derbyXAdb1" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<description>derby XA db1</description>
<property name="Password" value="1234"/>
<property name="DatabaseName" value="Q:\Data\Servers\Derby\db1"/>
<property name="User" value="nat"/>
</jdbc-connection-pool>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="derbyDB1" pool-resize-quantity="2" res-type="javax.sql.DataSource" steady-pool-size="8">
<description>derby db1</description>
<property name="Password" value="1234"/>
<property name="DatabaseName" value="Q:\Data\Servers\Derby\db1"/>
<property name="User" value="nat"/>
</jdbc-connection-pool>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.EmbeddedDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="derbyDB1pool" pool-resize-quantity="2" res-type="javax.sql.DataSource" steady-pool-size="8">
<property name="AttributesAsPassword" value="false"/>
<property name="Password" value="1234"/>
<property name="DatabaseName" value="Q:\Data\Servers\Derby\db1"/>
<property name="LoginTimeout" value="0"/>
<property name="User" value="nat"/>
</jdbc-connection-pool>
</resources>
What exactly did you add to domains/domain1/lib/ext?
1 file, derby.jar. Thanks again. -nat
Also, see if you can connect using the Network Server.
Lance Nat Gross wrote:
I have now also tried the cmd line, asadmin, and here are the similar results.
======================== E:\>asadmin list-jdbc-connection-pools --user admin --password 123 __TimerPool PointBasePool derbyXAdb1 derbyDB1 Command list-jdbc-connection-pools executed successfully.
E:\>asadmin ping-connection-pool --user admin --password 123 derbyDB1 org.apache.derby.impl.jdbc.EmbedSQLException CLI137 Command ping-connection-pool failed.
E:\>asadmin ping-connection-pool --user admin --password 123 derbyXAdb1 org.apache.derby.impl.jdbc.EmbedSQLException CLI137 Command ping-connection-pool failed.
E:\> ======================= At least we can rule out the gui.
I just noticed that derby.log (in the derby home) is a bit 'funny'.
----------------------------------------------------------------
2004-12-28 20:28:31.437 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.0.2.1 - (106978): instance c013800d-0101-1b5d-70a9-000062d71abd
on database directory Q:\Data\Servers\Derby\db1
Database Class Loader started - derby.database.classpath='' ================= And the deerby.log in ....domain1/config is even funnier:
2004-12-28 21:56:16.187 GMT: Shutting down instance c013800d-0101-1bad-e46d-000002911f60 ----------------------------------------------------------------
2004-12-28 22:01:52.703 GMT: Shutting down instance a816c00e-0101-1bad-e46d-000002911f60 ----------------------------------------------------------------
2004-12-28 22:02:36.687 GMT: Shutting down instance 601a400f-0101-1bad-e46d-000002911f60 ----------------------------------------------------------------
2004-12-28 22:03:29.375 GMT: Shutting down instance f81e0010-0101-1bad-e46d-000002911f60 ----------------------------------------------------------------
2004-12-28 22:03:52.421 GMT: Shutting down instance 80220011-0101-1bad-e46d-000002911f60
============================================= Nothin else in the log.
I hope I am doing something real silly, and I will soon yell why I wasted everyone's time.
In the interim...
Thanks again -nat
