Hi Tyler,
/2009-01-07 10:44:59,172 ERROR
[org.hibernate.util.JDBCExceptionReporter] - Protocol corruption while
trying to send command: 0. Check the previous command/
/18s time shift detected, from Wed Jan 07 10:44:40 EST 2009 to Wed Jan
07 10:45:00 EST 2009/
/Brutal changes of date/time can lead to erroneous controller failure
detections!/
/29s time shift detected, from Wed Jan 07 10:44:29 EST 2009 to Wed Jan
07 10:45:00 EST 2009/
/Brutal changes of date/time can lead to erroneous controller failure
detections!/
We have the server running on NTP. How such a time shift occurred is
beyond me. Having briefly gone through the source code, I noticed that
tweaking ControllerTimeout can make the Sequoia more tolerant once a
time shit is detected.
Where can I change ControllerTimeout and is this the proper way to go
around the issues? Thanks!
Actually this timeout is a setting in the Sequoia driver. There is
unfortunately no option to disable it right now but you can put
extremely large values to overcome that issue.
You can set these 2 properties:
protected static final String
PING_DELAY_IN_MS_PROPERTY = "pingDelayInMs";
protected static final String
CONTROLLER_TIMEOUT_IN_MS_PROPERTY = "controllerTimeoutInMs";
The default values are:
/**
* Default interval in milliseconds between two pings of a controller. The
* default is 1000 (1 second)
*/
public static final int
DEFAULT_PING_DELAY_IN_MS = 1000;
/**
* Default timeout in milliseconds after which a controller is
considered as
* dead if it did not respond to pings. Default is 25000 (25 seconds).
*/
public static final int
DEFAULT_CONTROLLER_TIMEOUT_IN_MS = 25000;
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [email protected]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
