OPENDJ-3309 Better handling of unexpected messages in the ReplicationServer listener thread
| | |
| | | // We did not recognize the message, close session as what |
| | | // can happen after is undetermined and we do not want the server to |
| | | // be disturbed |
| | | logger.error(ERR_REPLICATION_UNEXPECTED_MESSAGE, |
| | | session.getRemoteAddress().toString(), |
| | | (msg == null) ? "(null)" : msg.getClass().getSimpleName()); |
| | | session.close(); |
| | | return; |
| | | } |
| | | } |
| | | catch (Exception e) |
| | |
| | | in domain "%s" from this directory server DS(%d): no remote directory servers exist |
| | | ERR_FULL_UPDATE_MISSING_REMOTE_299=Cannot start total update \ |
| | | in domain "%s" from this directory server DS(%d): the remote directory server DS(%d) is unknown |
| | | ERR_REPLICATION_UNEXPECTED_MESSAGE_300=New replication connection from %s started with unexpected message %s and is \ |
| | | being closed |