Weblogic does not start, java.lang.NumberFormatException, EmbeddedLDAP

I encountered the following exception when trying to start our AdminServer today:

<May 30, 2013 1:04:27 PM CEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
 at java.lang.Integer.parseInt(Integer.java:454)
 at java.lang.Integer.parseInt(Integer.java:527)
 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
> 
<May 30, 2013 1:04:27 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> 
<May 30, 2013 1:04:27 PM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> 
<May 30, 2013 1:04:27 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

This does not really explain what went wrong, but the solution is to remove the replicas.prop file and restart the AdminServer again.

The replicas.prop file is located at :

$DOMAIN/servers/AdminServer/data/ldap/conf/replicas.prop

Rename (move) replicas.prop to replicas.prop.bak and retry the startWeblogic. In my case this solved the not starting server.

Advertisements

11 thoughts on “Weblogic does not start, java.lang.NumberFormatException, EmbeddedLDAP

  1. Ulric

    I had same problem here.
    Your solution has also solved my not starting server. After taking a look at the content of file :
    before : empty
    after : it contains “replica.num=0”
    I think we could have also put this line in the file instead of removing it.
    I still wonder why this file became suddenly empty.
    Anyway, thanks a lot !

  2. KS

    The problem occurred when the machine ran out of disk space while applying the latest Oracle Patch. replicas.prop file was truncated and when the server restarted, replicas.prop had about 40 lines. I think adding just one line to the file would have had adverse effect. The correct solution I believe is just renaming or deleting the truncated file.

    In our case, renaming the file worked like a charm, thank you for posting the solution.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s