1 Reply Latest reply on Mar 14, 2002 11:45 AM by geoff webb

    MDB Broken but used to work (Cannot get a client ID)?

    geoff webb Newbie

      OK so here is the scenario. I have a remote server running JBoss and acting as a message queing/topic scheduling machine. I have a couple of other JBoss instances on two other machines (One a publisher and one a subscriber, via MDB). This setup was working great until recently (power outage took down the remote machine). The problem is that now I can't get any machines to connect to the remote topic. I cant for the life of me see what has changed in the configuration as nothing was edited after the power outage. The stack trace from any attempt to connect to remote topic is shown below.

      I can connect to the remote naming service (remote:1099) but for some reason cant connect to the remote JMS topics - Cant get client ID?

      I can connect to the topic on the machine itself but not from any other machine on the network?

      Am I missing something simple here? Could there be an OS level networking issue here that I am missing?

      Any help/insight would be greatly appreciated!

      Geoff Webb

      Using: JBoss 2.4.4 on redhat 6.2 with jdk 1.3

      STACK TRACE:
      ------------
      org.jboss.mq.SpyJMSException: Cannot get a client ID: Connection refused
      at org.jboss.mq.Connection.askForAnID(Connection.java:439)
      at org.jboss.mq.Connection.(Connection.java:122)
      at org.jboss.mq.Connection.(Connection.java:145)
      at org.jboss.mq.SpyConnection.(SpyConnection.java:58)
      at org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFactory.java:62)
      at com.mysite.test.jms.HelloSubscriber.(HelloSubscriber.java:71)
      at com.mysite.test.jms.HelloSubscriber.main(HelloSubscriber.java:162)
      linked exception is:
      java.net.ConnectException: Connection refused
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
      at java.net.Socket.(Socket.java:273)
      at java.net.Socket.(Socket.java:127)
      at org.jboss.mq.il.oil.OILServerIL.createConnection(OILServerIL.java:254)
      at org.jboss.mq.il.oil.OILServerIL.checkConnection(OILServerIL.java:248)
      at org.jboss.mq.il.oil.OILServerIL.getID(OILServerIL.java:95)
      at org.jboss.mq.Connection.askForAnID(Connection.java:434)
      at org.jboss.mq.Connection.(Connection.java:122)
      at org.jboss.mq.Connection.(Connection.java:145)
      at org.jboss.mq.SpyConnection.(SpyConnection.java:58)
      at org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFactory.java:62)
      at com.mysite.test.jms.HelloSubscriber.(HelloSubscriber.java:71)
      at com.mysite.test.jms.HelloSubscriber.main(HelloSubscriber.java:162)

        • 1. Re: MDB Broken but used to work (Cannot get a client ID)?
          geoff webb Newbie

          OK, so I think I fixed it. After finally being able to see more than one result in the forum search, I tracked down similar issues people have had. It all rests on the local HOSTAME and entries in /etc/hosts which I thought I had ruled out. Alas there was a rogue entry! Silly me.

          HOSTNAME now maps (via /etc/hosts) to an address routable by all hosts wishing to connect to the machine acting as the message queu/topic handler.

          Anyhoos, it appears to work now. Can't for the life of me think why a reboot changed the settings as it did? Also, kickin myself for posting too early ;)

          Laters.

          Geoff