Issue: When you start WebLogic Server instance, the server would not come up and the start script hangs.
Symptoms:
In the /servers/AdminServer/logs/Adminserver.log you would find the following error.
####<Aug 27, 2009 3:47:58 PM EDT> <Critical> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478485> <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:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 27, 2009 3:47:58 PM EDT> <Notice> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478508> <BEA-000365> <Server state changed to FAILED>
####<Aug 27, 2009 3:47:58 PM EDT> <Error> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478509> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Aug 27, 2009 3:47:58 PM EDT> <Notice> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478511> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Solution:
When you see above error, please check
1. if the disk space is full
2. if disk space is fine, then delete the following file
/servers/AdminServer/data/ldap/conf/replicas.prop
and restart the server. WLS sometimes corrupts the file replicas.prop and is often results in above error
Thursday, August 27, 2009
Subscribe to:
Post Comments (Atom)
20 comments:
Thanks a lot. I checked the disk space and it was good. Then I removed the file you mentioned in step 2 and restarted the servers. It worked fine.
amipanda:
Glad to know that it helped
thanks it sis work
Thanks it solved my problem too renamed the file replicas.prop and restarted admin
Thanks... It works !!!
Thanks....It works
Thanks it worked...
Thanks a lot. It helped.
Thanks a lot
It worked.
THANK YOU VERY MUCH
Thanks a lot it works
Hi lekha....
your solution is excellent....
Can you please let me know the link between the error and relicas.prop file.
Thanks a lot, it worked!! Rahul
Thanks a lot, it worked! Rahul
Thanks a lot for the information..It saved a lot of time for us..
Thanks a ton for ur valuable help..It saved lot of time..
Thanks a lot, this solution worked like a magic.
Awesome... it worked, Thank you!
Awesome... it worked, Thanks!
Thanks a lot!
Post a Comment