Operating System - HP-UX
1833792 Members
2161 Online
110063 Solutions
New Discussion

Clustering WebLogic Failure

 
Bibi
Occasional Contributor

Clustering WebLogic Failure

Hi, I've received this error during start up. It is explaning that the at startup I tried to bind more than once from two or more servers. However, I'm still not certain of the cause of failure. Can anyone explain by looking at the log below what may have caused the error.

We are running WebLogic 8.1
-----------------------------------------------
Starting WebLogic Server ....
Connecting to http://sgbolton.sgp.hp.com:8011/...

Starting Cluster Service ....

















java.net.SocketException: socket closed
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:365)
at weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:145)
at weblogic.cluster.MulticastManager.execute(MulticastManager.java:298)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
java.lang.NullPointerException
at weblogic.cluster.RemoteMemberInfo.processAttributes(RemoteMemberInfo.java:193)
at weblogic.cluster.AttributeManager.receiveAttributes(AttributeManager.java:56)
at weblogic.cluster.AttributesMessage.execute(AttributesMessage.java:22)
at weblogic.cluster.MulticastReceiver$1.execute(MulticastReceiver.java:124)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
./startManagedWebLogic.sh[176]: 21837 Killed
WebLogic Java Process PID:
1 REPLY 1
Rajeev Tyagi
Valued Contributor

Re: Clustering WebLogic Failure

Bibi,

It looks like a conflict for port 8011 and 8012 which are already in use. Also looks like your adminserver url is http://sgbolton.sgp.hp.com:8011 which is port 8011. If it is on the same server where you are trying to start managed server port conflict will happen.