Number Format Exception while starting WebLogic Server

Ok, this has occurred way too many times recently in our environment. This usually happens if your machine is running low on space and WebLogic Server corrupted a file in the embedded LDAP.
To fix this problem you can delete the file /servers//data/ldap/config/replicas.prop or add ‘replica.num=0′ to replicas.prop file.
> NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>

7 Responses to “Number Format Exception while starting WebLogic Server”

  1. demenis says:

    It’s working… Thanks man!

  2. Uze says:

    I had another weird numerical error, but it fixed it too, thanks!

  3. Satya Ghattu's Blog says:

    good to hear my post helped you …

  4. Susan says:

    I recently came across your blog and have been reading along. I thought I would leave my first comment. I don’t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.

    Susan

    http://8080proxy.com

  5. sghattu says:

    Glad you like it.

  6. Larry Wren says:

    Our disk had a bad sector last night and had to be replaced and our WL filesystem restored.
    I kept running into this same error when trying to start the Admin server. I was warm (looking in ~ldap/ldapfiles) but could not fix it. Once I removed the ~ldap/conf/replicas.prop file after reading this the admin svr booted fine. Thanks a lot.