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