Fix for issue 2823 : Replication Heartbeat thread dies
A break statement is badly positionned in the ReplicationMonitor run method
and can cause the heartbeat Monitor thread to die to quickly
| | |
| | | * CDDL HEADER END |
| | | * |
| | | * |
| | | * Portions Copyright 2007 Sun Microsystems, Inc. |
| | | * Portions Copyright 2007-2008 Sun Microsystems, Inc. |
| | | */ |
| | | |
| | | package org.opends.server.replication.plugin; |
| | |
| | | // Heartbeat is well overdue so the server is assumed to be dead. |
| | | logError(NOTE_HEARTBEAT_FAILURE.get(currentThread().getName())); |
| | | session.close(); |
| | | break; |
| | | } |
| | | else |
| | | { |
| | | gotOneFailure = true; |
| | | } |
| | | break; |
| | | } |
| | | else |
| | | { |
| | |
| | | heartbeatThread = new HeartbeatThread( |
| | | "replication Heartbeat to " + serverURL + |
| | | " for " + this.baseDn, |
| | | session, heartbeatInterval); |
| | | session, heartbeatInterval/3); |
| | | heartbeatThread.start(); |
| | | } |
| | | |