Last updated on AUGUST 21, 2016
Applies to:Oracle Communications Configuration Management - Version 5.2.3 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Jun-2014***
Attempting to start the CM system fails. The startup procedure seems to fail and the user cannot login to the configuration management server in the usual manner.
The user also cannot login to the Weblogic console either on
The system was started using the command
Results in the following output in the nohup.out file
<Jul 30, 2009 5:47:36 PM SAST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /opt/bea92/license.bea>
<Jul 30, 2009 5:47:36 PM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 30, 2009 5:47:36 PM SAST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jul 30, 2009 5:47:36 PM SAST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea92/user_projects/domains/CMDomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<Jul 30, 2009 5:47:38 PM SAST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jul 30, 2009 5:47:40 PM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jul 30, 2009 5:47:40 PM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
log4j:WARN No appenders could be found for logger (org.apache.tapestry.RedirectFilter).
log4j:WARN Please initialize the log4j system properly.
Checking if the ConfigManagement.properties file is present
Subsequently the output stops here. Weblogic does not start, the user cannot login to the application or the weblogic console
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms