My Oracle Support Banner

Timeout Starting Weblogic Managed Server (Doc ID 2251553.1)

Last updated on JULY 20, 2018

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

A Timeout is occurring when starting the WebLogic Managed Server. The cluster resources start without a problem except for the Managed Server.

The following error is thrown.

$ crsctl start res weblogic_app
CRS-2672: Attempting to start 'weblogic_app' on 'medasapm01'
[weblogic_app] opcion start !Verificando procesos de weblogicPID :info: START WebLogic ASAP ASAP-SVR02ejecutando : nohup ./startManagedWebLogic.sh ASAP-SVR02 http://xxxxxxx:7010 2>&1 </dev/null | cat >> /opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out &LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out18LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out17LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out16LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out15LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out14LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out13LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out12LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out11LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out10LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out9LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out8LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out7LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out6LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out5LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out4LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out3LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out2LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out1LOGFILE :/opt/oracle/config/logs/ASAP-SVR02/ManagedServer.out0ERROR:

Timeout starting Weblogic Managed

<Apr 4, 2017 6:06:02 AM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Apr 4, 2017 6:06:02 AM COT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Apr 4, 2017 6:06:02 AM COT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/oracle/config/logs/ASAP-SVR02.log is opened. All server side log events will be written to this file.>
<Apr 4, 2017 6:06:04 AM COT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Apr 4, 2017 6:06:06 AM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Apr 4, 2017 6:06:06 AM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
/opt/oracle/config/domain/tigo_asap/bin/startWebLogic.sh: line 199:  8804 Killed                  ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}

 

Changes

 

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.