From: <glassfish_at_javadesktop.org>
Date: Mon, 15 Feb 2010 09:08:38 PST
w.r.t GlassFish, unless the pool (resource) is used by an application in server runtime (eg: servlet, ejb), pool will not be initialized (no connections will be created).
1) You can enable jdbc-connection-pool monitoring and verify the same.
2) eg:
http://fisheye4.atlassian.com/browse/glassfish-svn/trunk/v2/appserv-tests/devtests/jdbc/switchoffACCconnpooling
above test-case uses the connection pool in AppClient, when executed (against Derby), around 90 connections will be created, but once the client finishes the test, all of the connections will be closed within a minute or so, and
netstat -a | grep 1527 | wc -l will show as "1" which is the Derby Server itself.
[Message sent by forum member 'jr158900' (Jagadish.Ramu_at_Sun.com)]