Recovery log does not correctly invalidate prepared statements when idle
connection is timed out
------------------------------------------------------------------------------------------------
Key: SEQUOIA-974
URL: https://forge.continuent.org/jira/browse/SEQUOIA-974
Project: Sequoia
Type: Bug
Components: Recovery Log
Versions: Sequoia 2.10.9
Reporter: Robert Hodges
Assigned to: Robert Hodges
Fix For: sequoia 2.10.10
The LoggerThread prepared statements provided by getUpdatePreparedStatement()
and getLogPreparedStatement are not correctly invalidated when the JDBC
connection is timed out in RecoveryLog.invalidateInternalConnection(). This
causes unnecessary and confusing errors in the log because we try to use cached
prepared statements that are attached to a dead connection that has been
invalidated.
Also, it is possible that it is preventing connections from being properly
garbage collected when they are invalided, since there may be a backwards
reference from the JDBC connection.
This should be corrected by moving the prepared statements into the RecoveryLog
and synchronizing with connection invalidation.
--
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
