Have a doubt this time on JDBC Connection pooling. I have an application which connects to JDBC via a DSN named jdbc/FCRDSN created in Websphere App Server 5.1 and the connection timeout by default has been set to 180(seconds), the problem comes when this timeout reaches and my application throws a StaleConnectionException. I have browsed internet , however did not get satisfactory answers.
What i did for Solution : Increased the timeout which is 180 to 1800, which i thought would be good 30 minutes, but it doesnt happen the way i expected and it still throws the above said Exception.
Requirement : I am trying to find a solution to this in which i can set the connection timeout to Infinity and it wont matter much since this is my local development setup. I have read Servelts in which we can set <session-timeout> in indefinate, is there a similar kind of thing for JDBC as well ?
Thanks in advance,
Yogendra N Joshi.
Meri Zindagi Hain Tab Tak.. Jab Tak Tera Sahara.... Har Taraf Tu Hi Tu Hain SAI Tera Hi Hain Nazara.....
Paul Sturrock wrote:Are you closing connections when you are finished with them? A connection that is in use will not time out.
thanks for your reply. Actually what happens is the software (WAS 5.1 ) which i am using was a trial version and it has expired now and whenever i want to use it i need to backdate my computer system time. WHen i do that my it works fine.
After sometime, according to the company local policy, my system date again becomes today's date and henceforth if i try using it, it fails with StaleConnectionException