Thursday, August 27, 2009

WebLogic Server does not start

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




20 comments:

Anonymous said...

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.

Anamika said...

amipanda:
Glad to know that it helped

Unknown said...

thanks it sis work

Unknown said...

Thanks it solved my problem too renamed the file replicas.prop and restarted admin

Unknown said...

Thanks... It works !!!

Unknown said...

Thanks....It works

Unknown said...

Thanks it worked...

Sathish Bliss said...

Thanks a lot. It helped.

Unknown said...

Thanks a lot
It worked.

Unknown said...

THANK YOU VERY MUCH

Siva said...

Thanks a lot it works

sagar said...

Hi lekha....

your solution is excellent....

Can you please let me know the link between the error and relicas.prop file.

rahulk2602 said...

Thanks a lot, it worked!! Rahul

rahulk2602 said...

Thanks a lot, it worked! Rahul

Karvendan S said...

Thanks a lot for the information..It saved a lot of time for us..

Karvendan S said...

Thanks a ton for ur valuable help..It saved lot of time..

sireesh said...

Thanks a lot, this solution worked like a magic.

Eswar Chandra.Yadlapalli said...

Awesome... it worked, Thank you!

Eswar Chandra.Yadlapalli said...

Awesome... it worked, Thanks!

Yogesh said...

Thanks a lot!