We recently upgraded to glassfish 2.1 and suddenly last Friday we started seeing this exception in our logs:
[#|2009-09-01T07:14:53.558-0600|SEVERE|sun-appserver2.1|javax.enterprise.resource.resourceadapter|_ThreadID=39;_Thread
Name=httpSSLWorkerThread-8662-2;_RequestID=643098a7-d6a4-48f6-8a5a-3a78aff91c11;|RAR5031:System Exception.
javax.resource.ResourceException: This Managed Connection is not valid as the phyiscal connection is not usable
at com.sun.gjc.spi.ManagedConnection.checkIfValid(ManagedConnection.java:612)
And this one;
[#|2009-09-01T09:02:35.017-0600|SEVERE|sun-appserver2.1|javax.enterprise.system.core.naming|_ThreadID=41;_ThreadName=h
ttpSSLWorkerThread-8661-3;_RequestID=a0401efe-b948-49ad-b595-8146c08708d5;|NAM0004: Exception during name lookup : {0}
com.sun.enterprise.connectors.ConnectorRuntimeException: This pool is not bound in JNDI : heprodPool
at com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(Connec
torConnectionPoolAdminServiceImpl.java:1096)
We have "Connection Validation" set to required and are using the "auto-commit" Validation method. Tonight we are going to reset the validation method to "table".
We never had this problem with Glassfish 2.0, however school has just started so our servers and seeing an increased load.
As background we 5 domains on a glassfish instance, all domains are configure identically, including connection pools. We get this error all domains.
Any advice or links to documents / blogs would be a appreciated.
Thanks,
Bryan
Thanks,
Bryan
[Message sent by forum member 'bryanut' (bwooten_at_acs.utah.edu)]
http://forums.java.net/jive/thread.jspa?messageID=362620