[OPENDJ-3309] Replication server connection listener thread exits silently Created: 14/Sep/16  Updated: 03/Mar/20  Resolved: 21/Nov/16

Status: Done
Project: OpenDJ
Component/s: replication
Affects Version/s: 4.0.0, 3.5.0, 3.0.0, 2.6.4
Fix Version/s: 4.0.0

Type: Bug Priority: Major
Reporter: Chris Ridd Assignee: Chris Ridd
Resolution: Fixed Votes: 0
Labels: release-notes

Issue Links:
is backported by OPENDJ-3368 Backport OPENDJ-3309: Replication ser... Done
is backported by OPENDJ-3382 Backport OPENDJ-3309: Replication ser... Done
is backported by OPENDJ-4052 Backport OPENDJ-3309: Replication ser... Done
relates to OPENDJ-1135 DS sometimes fails to connect to RS a... Done
QA Assignee: Ondrej Fuchsik
Support Ticket IDs:


When an RS starts up it creates a thread to listen to the replication port. This creates a loop which exits when either the server is being shutdown, or the port is being reconfigured. The loop:

  1. accepts a new connection,
  2. does the SSL handshake, and then
  3. reads a ReplicationMsg.

If the ReplicationMsg is not a ServerStartMsg / ReplServerStartMsg / ServerStartECLMsg the thread returns silently, and effectively nothing is left to accept connections on the replication port.

There is absolutely no logging that this is happening, which seems like an omission. Something at ERROR level would be appropriate, because the replication service is now crippled.

We only determined this was a problem by comparing jstacks of a working server and of a broken server. It is not yet clear what message is being received that causes the thread to return.

Comment by Ondrej Fuchsik [ 17/Oct/16 ]

Can not reproduce the original issue and our logs in functional tests, do not contain new message.

Comment by Quentin CASTEL [X] (Inactive) [ 20/Nov/16 ]

modification of the status, in order to migrate the 'Zendesk ID' field to 'Support Ticket ID' field.

Generated at Wed Oct 21 10:31:05 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.