'FRDomain' Admin Server fails to start when the OC 5.0.1 Application Server is rebooted. (Doc ID 1922513.1)

Last updated on SEPTEMBER 02, 2014

Applies to:

Oracle Clinical - Version 5.0.1 and later
Information in this document applies to any platform.

Symptoms

i.

The automatic startup of OC services steps were followed as per section 'Setting Up Automatic Startup in Release 5.0.1 and Higher' which is documented in 'Creating Scripts to Automatically Start the Admin and Managed Servers for RDC Onsite and TMS (Doc ID 1628413.1)'.

 

ii.

Implementing the above steps means the FRDomain / OPADomain Admin Servers and their respective Managed Servers (ie OpaServer1WLS_FORMS and WLS_REPORTS) are started via the WebLogic Node Manager by Windows at Server Startup. 

 

iii.

However after restarting the OC 5.0.1 Application server only the 'OPADomain' Admin Server and the managed 'OpaServer1' server are RUNNING.  The 'FRDomain' Admin Server failed to start which in turn means the managed servers (WLS_FORMS and WLS_REPORTS) also failed to start. The following errors appeared in the FRDomain 'auto start' log files :

 

===================
autostartfrdomain2.err.txt :
===================
WARNING - Unable to create log file <C:\Oracle\MIDDLE~1\modules/../logs/wlst_20140820172059.log>.
Problem invoking WLST - Traceback (innermost last):
 File "c:\opapps50\config\autostartfrdomainscript.py", line 3, in ?
 File "<iostream>", line 22, in connect
 File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7001
Use dumpStack() to view the full stacktrace


=================
autostartfrdomain2.log:
=================
Successfully Connected to Node Manager.
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer'
Connecting to t3://localhost:7001 with userid weblogic ...
This Exception occurred at Wed Aug 20 17:21:54 CST 2014.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms