[ https://forge.continuent.org/jira/browse/SEQUOIA-855?page=all ]
Stephane Giron closed SEQUOIA-855:
----------------------------------
Resolution: Fixed
Fix Version: (was: Sequoia 2.10.5)
(was: Sequoia 3.0 beta3)
sequoia 2.10.10
Fixed in 2.10 branch
> Long idled persistent connections can see exceptions when sending a new
> request to MySQL
> ----------------------------------------------------------------------------------------
>
> Key: SEQUOIA-855
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-855
> Project: Sequoia
> Type: Bug
> Components: Core
> Versions: Sequoia 3.0 beta1, Sequoia 2.10.2
> Reporter: Stephane Giron
> Assignee: Stephane Giron
> Priority: Critical
> Fix For: sequoia 2.10.10
>
>
> If a client gets a persistent connection to sequoia against MySQL (or other
> databases that drop connection after an idle timeout), and does not execute
> queries against it for a long time, it will see an exception if the
> connection was closed by the underlying database.
> Trace of this kind of error :
> org.continuent.sequoia.common.exceptions.driver.DriverSQLException: Message
> of cause: No enabled backend to execute request 5
> at
> org.continuent.sequoia.driver.Connection.statementExecuteQuery(Connection.java:2849)
> at
> org.continuent.sequoia.driver.Statement.executeQuery(Statement.java:468)
> at
> org.continuent.sequoia.driver.Statement.executeQuery(Statement.java:441)
> Caused by:
> org.continuent.sequoia.common.exceptions.driver.protocol.ControllerCoreException:
> No enabled backend to execute request 5
> SerializableStackTrace of each cause:
> org.continuent.sequoia.common.exceptions.driver.protocol.ControllerCoreException:
> No enabled backend to execute request 5
> at
> org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.executeLPRF(RAIDb1_LPRF.java:207)
> at
> org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1_LPRF.execSingleBackendReadRequest(RAIDb1_LPRF.java:96)
> at
> org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.statementExecuteQuery(RAIDb1.java:160)
> at
> org.continuent.sequoia.controller.requestmanager.RequestManager.statementExecuteQuery(RequestManager.java:592)
> at
> org.continuent.sequoia.controller.requestmanager.distributed.DistributedRequestManager.execLocalStatementExecuteQuery(DistributedRequestManager.java:1351)
> at
> org.continuent.sequoia.controller.virtualdatabase.protocol.ExecRemoteStatementExecuteQuery.executeScheduledRequest(ExecRemoteStatementExecuteQuery.java:95)
> at
> org.continuent.sequoia.controller.virtualdatabase.protocol.DistributedRequest.handleMessageMultiThreaded(DistributedRequest.java:157)
> at
> org.continuent.sequoia.controller.virtualdatabase.DistributedVirtualDatabase.handleMessageMultiThreaded(DistributedVirtualDatabase.java:335)
> at
> org.continuent.hedera.adapters.MulticastRequestAdapterThread.run(MulticastRequestAdapterThread.java:99)
--
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
