Minimalistic replication-related changes
- Fix for a typo in replication.properties
- Avoid logging a message during shutdown (to avoid spurious traces)
| | |
| | | starting online full update for exporting suffix %s data to remote directory \ |
| | | server %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_144=Local directory server %s has \ |
| | | finished online full update for exporting suffix datat %s to remote directory \ |
| | | finished online full update for exporting suffix data %s to remote directory \ |
| | | server %s |
| | | NOTICE_TIMEOUT_WHEN_CROSS_CONNECTION_145=Timed out trying to acquire the domain \ |
| | | lock for %s. Connection attempt from replication server %s to local replication \ |
| | |
| | | { |
| | | // The socket has probably been closed as part of the |
| | | // shutdown or changing the port number process. |
| | | // just log debug information and loop. |
| | | Message message = ERR_EXCEPTION_LISTENING.get(e.getLocalizedMessage()); |
| | | logError(message); |
| | | // Just log debug information and loop. |
| | | // Do not log the message during shutdown. |
| | | if (shutdown == false) { |
| | | Message message = |
| | | ERR_EXCEPTION_LISTENING.get(e.getLocalizedMessage()); |
| | | logError(message); |
| | | } |
| | | } |
| | | } |
| | | } |