java.io.IOException: Invalid state file format. State file contents:
at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
at weblogic.nodemanager.server.ServerMonitor.loadStateInfo(ServerMonitor.java:475)
at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:139)
at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:255)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:103)
at weblogic.nodemanager.server.DomainManager.(DomainManager.java:55)
at weblogic.nodemanager.server.NMServer.initDomains(NMServer.java:219)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:199)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:355)
at weblogic.NodeManager.main(NodeManager.java:31)
then you need to remove the following file:
d:\bea\user_projects\domains\$DOMAIN_NAME\servers\C_0-S0\data\nodemanager\C_0-S0.state
16 comments:
Unfortunately for people who used to normal (read: Linux) error messages, those produced by Java are unclear and much too long. And - worst of all - they don't contain real cause.
A few days ago tried to run one Java program (TripleA). Got strange messages. With Google help I found out that it cannot resolve hostname. Indeed /etc/hosts didn't have entry for my machine name, but "cannot resolve hostname $somename" would be clear and enough...
thank you!
i solved my problem.
it's very useful information!
This solve mi problem too.
Thank you.
NICE
Thank you! solved on weblogic 11g too.
Esta solución también es válida para OFM 11.1.1.2
Feli
Muchas Gracias
Thanks
It should be noted that if you have more than one server running you have to delete all of the individual state files. In my case I had OID and OIF running on the same machine and I had to delete both to get NM happy.
Thanks, This Solved my problem
Thank you - I had this exact problem. I also agree with rozie's comment about java error messages in general - too much stack, not enough usefulness!
Thanks for the post. Very useful.
Beautiful... fixed my problem right away... thanks for the post!!!
Thanks for the post Banshee; this one's been a monster headache but your solution worked perfectly. Much appreciated.
Neil
Glad that this helped you, folks. @rozie, @Daniel: yeah, stacktrace is very useful for the original developer and/or somebody who has access to the source code, but true, in general it's just meddling the waters. And don't even get me started on ESB libraries like Spring Integration or Mule, who just pollute it with hundreds of lines of messages dispatching, reflection, AOP and similar crap.
Fantastic, thanks for the simple but priceless tip Banshee!!
Thanks you..solved my issue
thx!
Post a Comment