Hi 

I am getting stale connection during MS SQL Server failover ( happening automatically ), and during that time websphere throwing stale connection ( min connection is zero  ). I did all available setting for stale connection

min connection to 0 for connection pool

WebSphere Application Server data source properties

like 

I set SQL driver custom property logintimeout to 300 seconds ( Even after setting to 300, getting connection error in 15 seconds ( default ).. Is there any PMR or any solution to come out from this issue? Team is not interested to take care of this stale connection inside the java code.. Need suggestion

in fact there is a session Management properties StaleConnectionRetry, not helping me to fix..

Need your advicce to come out..

Hi can you please share below details:

1.WAS complete version.

2.WAS server logs .Error time-stamp

I think you are getting dependent stale connection issue. Once check purge policy is set to "entira pool" and restart the environment. Even still u r getting same issue means once check your driver type compatable has drivers for ur DB. 

I hope this may help you.thanks

If you are talking about DB stale connections, there is a setting under Data sources - <ds-name> - WebSphere Application server data source properties for "connection validation properties".  If you select Validate new connections & validate existing pooled connections, it will handle a stale connection.

Restart of server is required.

Thank you for all your replied.. 

Websphere version : 8.5.5.9

JDK 1.6

SQL Driver is 4.0

I did all the possibilities even Mr. Eric Clarke mentioned.. but it is not cleaning / purging the stale connection ( still wondering why ).. now IBM is telling..to stop the stale connection, need to update sql driver to 4.1 / 4.2. still my question is cleaning connection pool is IBM Responsible to do cleaning up by purge.. not able to see the logs proof to see the purge details..  Yes erver restart  will help but we are loosing transactions cos of stale connection.. still issue with in transaction connections. how to take care of that from websphere container?

If it helps, it sounds like you are doing all the right things. We are using 4.0 MS SQL driver without an issue.  The only other thing I could suggest is to run a trace on your jdbc connections so you have "all the details in exactly what is happening".  If you have done that as well then perhaps in your installation you do need the new driver. Good luck. I haven't run a trace for MS SQL but you should be able to find the information under "trouble shooting" => logs & trace in the console.  Good luck.

Have you checked your connection pool properties in the WAS console? i.e your Aged timeout, reap timeout, unused etc.