Weblogic AdminServer Does Not Start for Hyperion Planning

(Doc ID 1926691.1)

Last updated on JULY 28, 2016

Applies to:

Hyperion Planning - Version 11.1.2.0.00 and later
Information in this document applies to any platform.

Symptoms

Weblogic AdminServer will not start, terminating with a stack trace similar to this in 'AdminServer.log':

<Aug 31, 2014 10:58:48 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 31, 2014 10:58:48 AM GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 31, 2014 10:58:48 AM GMT> <Error> <Log Management> <BEA-170020> <The serverlog file /apps/Hyperion/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/logs/AdminServer.log could not be opened successfully.>
<Aug 31, 2014 10:58:49 AM GMT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
       at java.lang.Integer.parseInt(Integer.java:417)
       at java.lang.Integer.parseInt(Integer.java:499)
       at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1104)
       at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:242)
       at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
       Truncated. see log file for complete stacktrace
>
<Aug 31, 2014 10:58:49 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 31, 2014 10:58:49 AM GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 31, 2014 10:58:49 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


Changes

Triggered by running out of disk space

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