ConnectionClosingThread mechanism prevents daemon client threads to properly
close their connection
---------------------------------------------------------------------------------------------------
Key: SEQUOIA-950
URL: https://forge.continuent.org/jira/browse/SEQUOIA-950
Project: Sequoia
Type: Bug
Components: JDBC Driver
Versions: Sequoia 2.10.7, Sequoia 2.10.6, Sequoia 2.10.5, Sequoia 3.0
beta2, Sequoia 2.10.4, Sequoia 2.10.3, Sequoia 3.0 beta1, Sequoia 2.10.2,
Sequoia 2.10.1, Sequoia 2.10, Sequoia 2.9
Reporter: Gilles Rayrat
For connection pooling purpose, calling connection.close() doesn't close
immediately the connection. The ConnectionClosingThread will wait 5 minutes in
case the connection is re-used.
This is a problem when using daemon threads in clients, because the threads
will be stopped brutally by the jvm, and the close() will never be done,
leading to messages in controller such as:
WARN virtualdatabase.VirtualDatabaseWorkerThread.theVDB Client
(login:user,host:xyz closed connection with server)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
