[ https://forge.continuent.org/jira/browse/SEQUOIA-820?page=all ]
Mathieu Peltier closed SEQUOIA-820:
-----------------------------------
Resolution: Fixed
Successfully tested and backported in BRANCH_sequoia-2_10.
> If a client (using persistent connection) is killed during its connection
> establishment phase, this connection can remain "opened" on the cluster
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SEQUOIA-820
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-820
> Project: Sequoia
> Type: Bug
> Components: Core
> Versions: Sequoia 2.10.1, Sequoia 2.10, Sequoia 2.9
> Reporter: Stephane Giron
> Assignee: Mathieu Peltier
> Priority: Blocker
> Fix For: Sequoia 2.10.2, Sequoia 3.0 beta1
>
>
> This is what can be found in the controller log about this problem.
> 2006-10-04 18:01:52,212 ERROR
> virtualdatabase.VirtualDatabaseWorkerThread.vmuser I/O error during user
> authentication
> (java.io.EOFException)
> 2006-10-04 18:01:54,330 ERROR
> virtualdatabase.VirtualDatabaseWorkerThread.vmuser I/O error during user
> authentication (java.io.EOFException)
> 2006-10-04 18:02:19,999 WARN sequoia.controller.scheduler Waiting for 2 open
> persistent connections
> 2006-10-04 18:02:50,000 WARN sequoia.controller.scheduler Waiting for 2 open
> persistent connections
> If the disconnection happens after openPersistentConnection, the newly
> created connection will "remain" on the cluster and it will prevent from
> shutdowning the VDB.
--
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
