Issue details :- we got below exception during weblogic manged server and UI showing status FAILED TO START SERVER. xxx_server.out file saw below exception.. ..
--------------- Exception in .OUT logs
<Jul 30, 2014 8:33:56 PM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server soa_server1.>
<Jul 30, 2014 8:33:57 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at weblogic.rmi.cluster.BasicReplicaList.getPrimary(BasicReplicaList.java:90)
at weblogic.rmi.cluster.ClusterableRemoteRef.getPrimaryRef(ClusterableRemoteRef.java:155)
at weblogic.rmi.cluster.ClusterableRemoteRef.add(ClusterableRemoteRef.java:474)
Truncated. see log file for complete stacktrace
>
<Jul 30, 2014 8:33:57 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 30, 2014 8:33:57 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 30, 2014 8:33:57 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jul 30, 2014 8:33:57 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> With the current setting, only Email notifications will be sent; Notifications via voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to ALL in workflow-notifica tion-config.xml>
[TopLink Info]: 2014.07.30 20:33:58.166--ServerSession(301646737)--deferred_session logout successful
[TopLink Info]: 2014.07.30 20:33:58.166--ServerSession(304814922)--tracking_session logout successful
<Jul 30, 2014 8:33:59 PM EDT> <Error> <JMSPool> <BEA-169805> <A pooled JMS connection is being closed because an error was detected on the connection: Unknown reason>
<Jul 30, 2014 8:34:00 PM> <FINEST> <NodeManager> <Waiting for the process to die: 20768>
<Jul 30, 2014 8:34:00 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jul 30, 2014 8:34:00 PM> <FINEST>
---------------------------- OR ----------------------------------
Solution :- Please verify Disk space availabe in System[if yes the clean unnecessary files and make sure available disk space should be 20-40% of total disk space] then shutdown whole domain including node manager[NM] {FYI- I believe there is no command available to stop NM. Please kill it kill -9 [PID] }
NOTE:- Rolling restart doesn't help. must be stop whole domain and start
Step1:- Start NM then start Admin servers.
Step2:- Before start the Managed servers Clean tmp and cache folders under @DOMAIN_HOME/servers/xxx_server1/
it's worked for our environment all time[Please let me know if issue is not resolved..then will update this blog...]
No comments:
Post a Comment