启动weblogic提示BEA-000386错误,java.lang.NumberFormatException: null

之前启动weblogic的时候遇到一个问题

启动失败,提示信息如下

<2019-9-4 下午07时12分28秒 CST> <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
> 
<2019-9-4 下午07时12分28秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> 
<2019-9-4 下午07时12分28秒 CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> 
<2019-9-4 下午07时12分28秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> 

　

网上找到一种办法

原文:http://superhero.ninja/2013/05/30/weblogic-does-not-start-java-lang-numberformatexception-embeddedldap/

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.

删除你自己项目的weblogic域中 /servers/AdminServer/data/ldap/conf   目录下的 replicas.prop 文件,再重新启动就好了   (startWeblogic.sh)

转载于:https://www.cnblogs.com/dpxjf/p/11474867.html