[jboss-jira] [JBoss JIRA] Closed: (JBAS-5526) DB Connections established which fail check-valid-connection-sql do not immediatly close their connection
[ http://jira.jboss.com/jira/browse/JBAS-5526?page=all ]
Adrian Brock closed JBAS-5526.
------------------------------
Resolution: Done
This also effects other "initialization" done on the connections,
e.g. setting the transaction isolation level.
This has been fixed by catching all errors from connection initialization
in the resource adapters and closing the connection when one occurs.
I also fixed a similar issue in the JMS resource adapter, e.g. where the connection
could be constructed but the session creation throws an error.
DB Connections established which fail check-valid-connection-sql do
not immediatly close their connection
---------------------------------------------------------------------------------------------------------
Key: JBAS-5526
URL: http://jira.jboss.com/jira/browse/JBAS-5526
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA
Environment: Red Hat Enterprise 5.1, MS SQL Server 2005
Reporter: Dan Killey
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
When a DB connection is attempted to be created where it is configured with
new-connection-sql, if the socket/connection succeeds but the new-connection-sql statement
fails a connection remains open until GC. In a large volume environment this can lead to
many sockets being opened until GC occurs and can thus run into file handle limits.
If a valid TCP connection was established, but the SQL fails, I am suggesting the
connection should also be closed at the time of failure, not waiting till GC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira