|
This patch try to add the loginTimeout feature.
This is made by creating another thread that will call the _driver.connect(_connectUri, _props); The main thread will wait for it by using the Thread.join(timeout) method. If the join method returns by timeout and the connect didn't finished, then the main method will throw an SQLException "timeout". Anyway, for the moment, the second Thread will not be stopped, even if the Thread.interrupted() method is called. I see four alternatives here. If others have better ideas, please chime in.
1) Apply cleaned up version of the patch. I don't like the idea of spawning a thread in 1), 2) can already be accomplished in the connect string, 3) is redundant, so unless someone has a better idea, I think we should close as WONTFIX. I agree with Phil's analysis. Therefore, resolving as WONTFIX.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DBCP-218is fixed by adding a Javadoc comment.