[jira] Closed: (DBCP-287) Socket Connection Timeout Fix for Connection Pool management

["Phil Steitz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DBCP-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz closed DBCP-287.
----------------------------


> Socket Connection Timeout Fix for Connection Pool management
> ------------------------------------------------------------
>
>                 Key: DBCP-287
>                 URL: https://issues.apache.org/jira/browse/DBCP-287
>             Project: Commons Dbcp
>          Issue Type: Task
>         Environment: JDK 1.5 on Linux Tomcat 5.5.23 with DBCP
>            Reporter: Ajay Warrier
>
> I have an apache tomcat server configured in the Production with DBCP Connection Pool parameters configured to talk to the Database.
> The Application war files looks at the datasource that is setup in the context.xml to connect to the DB
> Now the issue is....There is a firewall between the Tomcat Server and the DB. and the firewall is programmed to timeout and disconnect any existing
> sockets after an hour of inactivity. When this happens , and a new connection is tried from the Tomcat Server to the DB, it fails as TOmcat still things that 
> the connection is active and tries to make an attempt on this Socket timed out connection and then it eventually times out.
> Here is a snippet from my context.xml
> <Resource name="jdbc/TESTDB" auth="Container" type="javax.sql.DataSource" driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@SERVER_NAME:1521:TEST_DB_SID" username="TEST1" password="TEST1" maxActive="200" maxIdle="10" maxWait="10000" removeAbandoned="true" removeAbandonedTimeout="60" logAbandoned="true"/>
> Can anyone help me resolve this issue? ..

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.