1 Reply Latest reply on Jan 27, 2007 11:46 PM by Ovidiu Feodorov

    Node0 cant' be killed or Cluster Configuration Problem?

    gerald zhou Newbie

      Hi all:
      I deploy jboss-messaging1.2 beta on jboss-4.0.2. Follow the cluster document, i create 4 node and startup this node from node0 to node4. When server started, i have catched this message:
      16:33:25,203 INFO [ServerPeer] JBoss Messaging 1.2.0.Beta1 server [0] started
      16:33:25,578 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 127.0.0.1:4543
      -------------------------------------------------------
      16:33:25,687 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered
      JMS:127.0.0.1:4543] got new view: [127.0.0.1:4396|5] [127.0.0.1:4396, 127.0.0.1:
      4407, 127.0.0.1:4433, 127.0.0.1:4543]
      16:33:25,703 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 127.0.0.1:4548
      -------------------------------------------------------
      16:33:26,437 INFO [ConnectionFactory] Connector socket://192.168.0.51:4457 has
      leasing enabled, lease period 10000 milliseconds

      Then i running my Queue Tester, It can send and receive message successful. But when i kill the node0 retesting that, it can't find any JMS server. Error as follow:
      0 ERROR jms.QueueMessage (QueueMessage.java:82) - init JMS Queue failed
      javax.naming.CommunicationException: Could not obtain connection to any of these urls: 192.168.0.51:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server 192.168.0.51:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.0.51:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1420)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:595)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)
      at com.travelco.jms.ContextHelper.getQueueFactory(ContextHelper.java:154)
      at com.travelco.jms.QueueMessage.init(QueueMessage.java:71)
      at com.travelco.jms.QueueMessage.(QueueMessage.java:48)
      at com.travelco.jms.QueueSenderTester.main(QueueSenderTester.java:11)
      Caused by: javax.naming.CommunicationException: Failed to connect to server 192.168.0.51:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.0.51:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:270)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1391)
      ... 7 more
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.0.51:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
      ... 8 more
      Caused by: java.net.ConnectException: Connection refused: connect
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
      at java.net.Socket.connect(Socket.java:452)
      at java.net.Socket.connect(Socket.java:402)
      at java.net.Socket.(Socket.java:309)
      at java.net.Socket.(Socket.java:211)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:240)
      ... 8 more