Bug #49732 Connection.isValid is often false
Submitted: 16 Dec 2009 6:53 Modified: 4 Nov 2022 20:29
Reporter: Matt Cheng Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:5.1.6 OS:Windows (2008)
Assigned to: Assigned Account CPU Architecture:Any

[16 Dec 2009 6:53] Matt Cheng 
Description:
For JDBC4Connection.isValid(int timeout)
Is it possible to spend too much time on the execution of pingInternal(false), so before timeoutTask.cancel() is executed , the timeoutTask has been scheduled and running?
Then next time connection.isValid always false.

How to repeat:
If the network connection quality of instability
[21 Dec 2009 10:03] Tonci Grgin 
Hi Matt and thanks for your report.

Looking into code, I'd say such situation is possible thus "Varified".

However, you are responsible to set appropriate values depending on your network quality and I am not sure if we can do anything at all regarding this.

Passed to Mark for final ruling.
[4 Nov 2022 20:29] Filipe Silva 
Posted by developer:
 
This should not be an issue anymore. If it is, then please re-file a bug providing a reproducible test case.