Server subsystem failed. Reason: java.lang.NumberFormatException: null

Posted on Friday, 28 September 2012 by Eric Elzinga

30 Comments BOOKMARK

Our admin server of the osb development environment failed to restart because of a full disk.
After cleaning up the admin server still wouldn’t start resulting in the next stack.

[code]

[/code]

Locate the file :
[code]
ORACLE_HOME/user_projects/domain/your_domaim_name/servers/AdminServer/data/ldap/conf/replicas.prop
[/code]
.. and remove it

In our case the file got corrupted (0byte file).
Removing the file, the file will get recreated with something like the next content :

[code]
[weblogic@my_machine conf]$ cat replicas.prop
#Generated property file
#Fri Sep 28 10:27:06 CEST 2012
replica.num=1
replica.0.name=OSB-MS1
replica.0.base=dc\=OSB
replica.0.port=7003
replica.0.hostname=my_hostname
replica.0.masterurl=ldap\://my_hostname\:7001/
replica.0.masterid=AdminServer
replica.0.secure=0
replica.0.binddn=cn\=Admin
replica.0.consumerid=OSB-MS1
[/code]

Share this Post:

Tagged with:

30 Responses to “Server subsystem failed. Reason: java.lang.NumberFormatException: null”

s reddy | December 29th, 2012 at 4:38 am

thanks a ton for ur help. it really helped us in solving the number format exception.

Kiran | January 10th, 2013 at 2:02 pm

Thanks Eric. It fixed my issue.

Lisa | July 22nd, 2013 at 5:53 pm

Thanks a million! Have been working with the vendor and nothing getting fixed…I am now back up and running!

Jahnavi | October 10th, 2013 at 3:37 pm

Thank you It worked .

KK | October 19th, 2013 at 1:57 pm

Thanks this worked.

Abhaya | March 3rd, 2014 at 5:45 am

Thanks Eric. It fixed my issue.

Siti | June 27th, 2014 at 4:47 am

Thanks. It fixed my issue.

sam | October 1st, 2014 at 6:32 am

thank you soo much

Prashant | October 13th, 2014 at 8:38 am

Thanks Eric, it worked for me.

Sudhakar | November 26th, 2014 at 6:33 am

WOW, great stuff. really appreciating

Wojtek | March 9th, 2015 at 6:47 am

THX, it worked for me too!

Ravi Kulkarni | June 23rd, 2015 at 1:15 pm

Thanks a lot, worked like charm.
I don’t necessarily have right credentials to look into these issues, but ended up in this situation. Exact same symptoms and reasons. /u01 got full and after UNIX team cleaned it up, weblogic was not starting.
Thanks

smvm | July 15th, 2015 at 11:43 pm

You are a champ, this article, brought my severup and running in 30 minutes

Evan Brown | September 8th, 2015 at 11:13 am

Thanks, this had me fix and running in 3 mins!! Thanks.

Angel | December 9th, 2015 at 2:29 pm

Awesome!! thanks for the help!!!!

Soa Java | healthtooth.com | February 24th, 2016 at 8:24 am

[…] Server subsystem failed. Reason: java.lang … – Thanks a lot, worked like charm. I don’t necessarily have right credentials to look into these issues, but ended up in this situation. Exact same … […]

AlexG | March 14th, 2016 at 10:16 am

Thanks man!!!!!

Margaret | March 24th, 2016 at 9:14 am

Great post! We ran into the exact scenario you ran into. Luckily,I ran into your post and this fix worked like a charm. Thanks for posting! You saved me hours of troubleshooting.

Kaarthi | April 4th, 2016 at 9:15 am

After removing the replicas.prop, when I restart the server it is not creating the file properly. Is there anyway we can create it manually?

Eric Elzinga | April 5th, 2016 at 1:50 pm

Is it a 0byte file after restart or does it contain any content ?

Becky Herrera | May 24th, 2016 at 12:49 pm

Thank you exactly what I needed!

V M | January 8th, 2017 at 2:19 pm

Ran into the same issue, and came across this post. Followed the exact steps and it fixed my issue.Thank you!

Miroslav | February 18th, 2017 at 5:35 pm

Good one, thanks. In addition, we had the issue with another corrupted file (adapters.os_xml), so we took it from backup dest:

cp /opt/oracle/middleware/oracle_common/modules/oracle.ovd_11.1.1/templates/adapters.os_xml /opt/oracle/middleware/user_projects/domains/FRSDomain/config/fmwconfig/ovd/default/adapters.os_xml

Cheers!

Dan | April 17th, 2017 at 11:28 am

Thank you so much, this fixed my issue.

Cesar | May 10th, 2017 at 4:05 pm

Eric, thanks for the information.
This resolved my issue.
Reggards,

Zach | September 26th, 2017 at 9:23 pm

You are the man, thank you

Gupta Rj | February 18th, 2018 at 12:10 am

HI Team,

Getting below exception and the above solution i tried but it did’t work. Kindly help.

All server side log events will be written to this file.>
<Server subsystem failed. Reason: java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at weblogic.protocol.ProtocolHandlerAdmin.getDefaultServerChannel(ProtocolHandlerAdmin.java:51)
at weblogic.server.channels.ChannelService.createServerChannels(ChannelService.java:506)
at weblogic.server.channels.ChannelService.initializeServerChannels(ChannelService.java:311)
at weblogic.server.channels.ChannelService.start(ChannelService.java:218)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at weblogic.protocol.ProtocolHandlerAdmin.getPriority(ProtocolHandlerAdmin.java:77)
at weblogic.server.channels.BasicServerChannelImpl.(BasicServerChannelImpl.java:485)
at weblogic.server.channels.ServerChannelImpl.(ServerChannelImpl.java:94)
at weblogic.server.channels.ServerChannelImpl.(ServerChannelImpl.java:85)
at weblogic.server.channels.ServerChannelImpl.createDefaultServerChannel(ServerChannelImpl.java:217)
Truncated. see log file for complete stacktrace
>