One problem we did have related to this was if the connections are going through a Firewall, the firewall can close the connections at a certain defined idletime, but the state of the connection(s) still indicate OPEN. We had to coordinate this timing, and close IDLE connections ourselves to maintain the proper state of the connection.
 
-----Original Message-----
From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 3:15 PM
To: [EMAIL PROTECTED]
Subject: Re: JDBC with oracle and timeouts

According to the "Oracle 9i DBA Handbook" (Oracle Press, 2002), p. 20, you can set the timeout length for the pool.
 
Mark
-----Original Message-----
From: john bell [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 2:13 PM
To: [EMAIL PROTECTED]
Subject: Re: JDBC with oracle and timeouts

Using JDBC thin driver we open a pool of connections to Oracle and after what seems a random time but probably is not the connections timeout if not used.  Can anyone advise please.
 

Reply via email to