[
https://jira.jboss.org/jira/browse/JBAS-6092?page=com.atlassian.jira.plug...
]
Brian Stansberry resolved JBAS-6092.
------------------------------------
Resolution: Done
This is done via the TimestampDiscrepancyWarnService configured in
deploy/cluster/timestamps-jboss-beans.xml. By default it logs a WARN if it detects a
discrepancy of > 2 minutes in the system clock of the node and another node. It can be
configured to log an ERROR instead, and the max discrepancy can be configured as well,
with ms precision.
TimestampDiscrepancyWarnService uses the general purpose TimestampDiscrepancyService as
its source of data on system clock differences. That service uses a group RPC over
HAPartition to check for system clock differences. The accuracy of the check is only as
good as the amount of time it takes to make the group RPC. So, this service should not be
configured to warn about very small differences.
Check and warn if system time is off on joining node
----------------------------------------------------
Key: JBAS-6092
URL:
https://jira.jboss.org/jira/browse/JBAS-6092
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Radoslav Husar
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.1.0.CR1
When new node joins the cluster, It can simply exchange time with other nodes. If the
time is off by significant number of seconds, it would warn the administrator to
synchronize the time on cluster machines. Since some services depend on having time
synchronized, this could help users to find this problem quickly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira