Always using DerbyPool
I wanted to create a DB2 Connection Pool and a datasource with v4 final.
Unfortunately my servlet did not use the DB2 pool but the Derby pool (see first exception).
Entry in domain.xml pointed correctly to DB2, but still Derby was taken:
OK, I hacked the Derby pool with the DB2 properties. I got a strange error No password credential found
but the solution from
(restart the server) helped and my servlet worked with DB2.
Googling the Exception below gives several hits, so this seems to be a quite old bug...
Can anybody confirm/reproduce the bug?
Update: linking jdbc/__default to the db2 pool fixes the problem, too. So it seems Glassfish always uses the default pool.
RAR5038:Unexpected exception while creating resource for pool DerbyPool. Exception : javax.resource.spi.ResourceAllocationException: Connection could not be allocated because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused.]]