I don't know if it is the same thing, but I added the following lines to
fix a problem I hat with the recoveryLog. I use mysql as recoveryDB. After
a while the recoveryLog tried to log into a closed connection. With
workaround works fine for me:
private void validateConnection() throws SQLException
{
try
{
logger.debug("Connectionvalidation process starts...Connections should
be "+connected);
if (connected == true){
connection.createStatement().execute("select 1");
}
}
catch (SQLException e)
{
logger.debug("Connectionvalidation process failed...");
connected = false;
}
if (! connected)
connect();
else if (lastAccessMillis > 0)
{
if ((lastAccessMillis + this.autoCloseTimeoutMillis) <
System.currentTimeMillis())
{
release();
connect();
}
}
}
best regards
Malte
> Recovery Log : RecoveryLogConnectionManager does not take into account
> autoCloseTimeoutMillis
> ---------------------------------------------------------------------------------------------
>
> Key: SEQUOIA-1059
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-1059
> Project: Sequoia
> Type: Bug
>
> Reporter: Stephane Giron
> Assigned to: Stephane Giron
>
>
> After autoCloseTimeoutMillis is reached, the recovery log connection
> should not be used anymore.
> However, this does not work for now and can lead to errors in case the
> recovery log database would close idle connections.
>
> --
> 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
>
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
