0 Replies Latest reply on May 26, 2008 12:16 PM by Jorge Morales

    Another JMS cluster config question

    Jorge Morales Master

      I have set up a 2 node cluster in one machine, as stated in the docs, and when I deploy an app that has a Queue defined and a consumer (which works fine in a cluster in 2 separate machines) I get the following errror:

      2008-05-26 17:58:56,449 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to 16.38.25.134:1100
      javax.naming.CommunicationException: Failed to connect to server 16.38.25.134:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 16.38.25.134:1100 [Root exception is java.net.ConnectException: Connection refused]]
       at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
       at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
       at javax.naming.InitialContext.lookup(InitialContext.java:351)
       at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:708)
       at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:184)
       at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:106)
       at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:577)
       at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:262)
       at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:512)
       at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
       at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:326)
       at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
       at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
       at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:389)
       at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:144)
       at com.hp.som.handlers.jms.QueueWrapper.createSession(QueueWrapper.java:89)
       at com.hp.som.handlers.jms.DestinationWrapper.sendMessage(DestinationWrapper.java:131)
      


      Do I have to change the NamingServicePort somewhere, as it seems it is using the defaults.
      Although I get this message, message seems to be dispatched to the queue. Don't know how!!!