OPADomain 'Node Manager' Process Unexpectedly Terminates and Puts The 'OPA_1' Managed Server In 'Failed' Status.
(Doc ID 2980169.1)
Last updated on OCTOBER 12, 2023
Applies to:
Oracle Thesaurus Management System - Version 5.2.0 and laterOracle Clinical - Version 5.2.0 and later
Oracle Clinical Remote Data Capture Option - Version 5.2.0 and later
Information in this document applies to any platform.
Symptoms
i.
'OPADomain Node Manager process terminates after some time which puts the '_OPA1' WLS Managed Server in 'Failed' status.
ii.
No informative error is logged in the Weblogic log files apart from stating the managed server has gone into 'Failed' status.
iii.
This causes issues when using the applications. For example 'Java exception' error appears when trying to run a TMS 'XDO' report.
iv.
'Automatic Startup' of Weblogic services has been configured as per the documented steps (click here to view).
v.
Now if the OPADomain Node Manager process is started manually from the command line then the process keeps running and never terminates.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |