weblogic集群无法启动,提示java.lang.NumberFormatException

我有两台weblogic9.2做的集群A,B,A是主服务器,B是受管服务器,后来通过脚本启动weblogic服务,A服务启动异常,经查后台的日志文件发现报错消息如下：

  

WebLogic Server throws java.lang.NumberFormatException: null from the Embedded LDAP
Posted on November 24, 2010 by maclean
Applies to:

Oracle Weblogic Server – Version: 9.0 to 10.3
Oracle Weblogic Server – Version: 9.0 to 10.3]
Information in this document applies to any platform.
Symptoms

The following exception appears on startup on the admin server. The admin server then fails to start up.
####<17-Jul-2009 10:24:02 o'clock GMT> <Critical> <WebLogicServer> <silvermoon> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1227111442502> <BEA-000386> <Server subsystem failed. Reason: java.lang.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)
Cause

This is something that happens infrequently and is the result of a corrupted file in the embedded LDAP. It can be caused when your system is starting to run low on disk space
Solution

There are two ways to fix this issue:

1) Delete the file /servers/<server_name>/data/ldap/config/replicas.prop

OR

2) Alter the replicas.prop file and add ‘replica.num=0′ to it.

Related posts:

    Java.Lang.Outofmemoryerror: Alloclargeobjectorarray When Deploying War
    Deadlock Detected On An Application Written In Cocoon Framework

This entry was posted in Uncategorized and tagged JAVA.LANG.NUMBERFORMATEXCEPTION, LDAP, WEBLOGIC. Bookmark the permalink.
← IndexOutOfBoundsException When Booting Managed Servers into Cluster in WebLogic Server (WLS)

 

通过上述的日志消息以及从网上找的一些资料,发现有两个办法可以解决

1) Delete the file /servers/<server_name>/data/ldap/config/replicas.prop

OR

2) Alter the replicas.prop file and add ‘replica.num=0′ to it.