Kbase P126766: Remote OpenEdge Management containers on Windows machines go offline randomly and may not reconnect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/07/2009 |
|
Status: Verified
SYMPTOM(s):
Remote OpenEdge Management containers on Windows machines go offline randomly and may not reconnect even after restart of primary AdminServer.
Remote Fathom Management containers on Windows machines go offline randomly and may not reconnect even after restart of primary AdminServer.
Primary AdminServer was never stopped and is still responsive.
Remote AdminServer was never stopped and is still responsive.
Fathom Admserv log file contains errors regarding connection to remote container:
SvcControlCmd.connectToService() failure: Unable to connect to the service process at rmi://hostname:20931/mycontainer(after 2 retries) (8171)
.() failure: (8171)
FACT(s) (Environment):
All Supported Operating Systems
Fathom Management 2.x
Fathom Management 2.1A
Fathom Management 3.x
OpenEdge Management 3.1A 32-bit
OpenEdge Management 3.1A 64-bit
OpenEdge Fathom Category: Management
CAUSE:
Bug# OE00158603
FIX:
Upgrade to OpenEdge 3.1B03 or 3.1C.
If upgrade to 3.1B03 is not possible, a partial workaround exists which is to periodically restart the primary AdminServer.
It has been seen in some cases when using the workaround with multiple remote Fathom / OpenEdge Management containers (remotely monitored machines) the previously offline container will go online and the previously online container may change state to offline.