Feedback
Did this article resolve your question/issue?

   

Article

OpenEdge Replication Agent and Server terminates after connection failure

Information

 
TitleOpenEdge Replication Agent and Server terminates after connection failure
URL NameP156979
Article Number000132251
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: Replication
Question/Problem Description
OpenEdge Replication Agent terminates after connection failure with errors in the source log file.

 
Steps to Reproduce
Clarifying Information
Database Target and Replication Server can be restarted without errors.
Error MessageConnection failure for host <host_name> port <port> transport <transport_name>. (9407)
A communications error <error-code> occurred in function <function-name> while receiving a message. (10492)
A communications error -157 occurred in function rpNLA_PollListener while receiving a message. (10492)

A TCP/IP failure has occurred. The Agent's will enter PRE-TRANSITION, waiting for connection from the Replication Server. (11699)
PROGRESS AppServer network protocol mismatch. (5565)
A communications error <error-code> occurred in function <function-name> while receiving a message. (10492)
A communications error -4010 occurred in function rpNLA_PollListener while receiving a message. (10492)
Unexpected error <error-code> returned to function <function-name>. (10504)
Unexpected error -4010 returned to function rpAGT_AgentLoop. (10504)
A communications error <error-code> occurred in function <function-name> while sending <message-id>. (10491)
A communications error -155 occurred in function rpNLA_SendAgentError while sending AGENTERROR. (10941)
The Fathom Replication Agent is shutting down. (10482)
The Fathom Replication Agent <agent-name> is ending. (10506)
OpenEdge Replication Server terminates after connection failure with the following errors in the source log file:
Connection failure for host <host_name> port <port> transport <transport_name>. (9407)
A communications error <error-number> in <function-name>. (11713)
A communications error -4008 in rpCOM_RecvMsg. (11713)
A communications error <error-code> occurred in function <function-name> while receiving a message. (10492)
A communications error -157 occurred in function rpNLS_PollListener while receiving a message.
The Fathom Replication Server is beginning recovery for agent <agent-name>. (10661)
The Fathom Replication Server is beginning recovery for agent agent1. (10661)

Connecting to Fathom Replication Agent <agentname>. (10842)
Connecting to Fathom Replication Agent agent1. (10842)

The Fathom Replication Agent <agent-name> cannot be contacted by the database broker on host <hostname>, port <port-number>. (10496)
The connection attempt to the Fathom Replication Agent <agentname> failed. (10397)
The connection attempt to the Fathom Replication Agent agent1 failed. (10397)
The Fathom Replication Server was unable to reconnect to agent <agent-name>. Recovery for this agent will not be performed. (10697)
The Fathom Replication Server will shutdown but the source database will remain active. (10698)
The Fathom Replication Server is ending. (10505)
Defect/Enhancement Number
Cause
A break in the TCP/IP connection between the OpenEdge Replication server and its Agents has occurred.
Resolution
This is expected behavior.  No immediate action is required as long as target database and Replication Server can be restarted without errors.

Since OpenEdge 11.6, the Replication Agent can be restarted without having to restart the target database. For further information refer to Article:
If the Replication Server shutdown within a very short time frame of the error occurring, the connect-timeout parameter might be set too low and may need to be increased to allow the Replication Server to retry for a longer period of time before shutting down.  To configure the appropriate connect-timeout refer to Article: If regular recurrences of the network fault occur, consider using a 3rd party tool such as Wireshark to assist in finding out what is causing the network issue.  It is beyond the scope of Progress Technical Support to assist with analyzing or resolving network faults.  A known issue in this area are:

1.   When there are Network changes implemented while the replication ports are in use, firewall routing is a typical example. Refer to Article: 2.   When the replication ports in use get sent packets from non-Progress clients, Port Scanning is is the most typical example. Error 5565 is usually pre-ceeded by error 9407 when this is the case. Refer to Article:
Workaround
Notes
Last Modified Date1/17/2019 8:27 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.