1 Reply Latest reply on Jun 12, 2009 1:42 PM by papiyamisra

    In Jboss Logs -

      I have an application X that reads the messages from Topics in applications A and B.

      When A is shutdown, I keep getting messages in the log of X - "Trying to connect to JMS". This is expected.

      However, when B is shut down, I recieve a few "Trying to connect" messages and then I see "Reconnected to JMS" in the log of X. Also, if I now start B, the messages are not processed at all. I have to restart X to process all the pending messages.

      Here is the excerpt of the log of application X when application B is shutdown.Note the last statement. Also, please let me know if I can provide more info to troubleshoot.

      2009-06-11 10:48:30,661 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to ApplicationB:1099
      javax.naming.CommunicationException: Failed to connect to server otciq1.test.ps:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server otciq1.test.ps:1099 [Root exception is java.net.ConnectException: Connection refused]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
      at javax.naming.InitialContext.lookup(InitialContext.java:392)
      at org.jboss.ejb3.mdb.MDB.innerCreateTopic(MDB.java:443)
      at org.jboss.ejb3.mdb.MDB.innerCreate(MDB.java:342)
      at org.jboss.ejb3.mdb.MDB.innerStart(MDB.java:225)
      at org.jboss.ejb3.mdb.MDB$ExceptionListenerImpl.onException(MDB.java:1133)
      at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1320)
      at java.lang.Thread.run(Thread.java:619)
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server otciq1.test.ps:1099 [Root exception is java.net.ConnectException: Connection refused]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
      ... 10 more
      Caused by: java.net.ConnectException: Connection refused
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
      at java.net.Socket.connect(Socket.java:519)
      at java.net.Socket.connect(Socket.java:469)
      at java.net.Socket.(Socket.java:366)
      at java.net.Socket.(Socket.java:267)
      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:239)
      ... 10 more
      2009-06-11 10:48:30,688 DEBUG [org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory] Extracting SpyConnectionFactory from reference
      2009-06-11 10:48:30,689 DEBUG [org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory] The GenericConnectionFactory is: GenericConnectionFactory[server=org.jboss.mq.il.uil2.UILServerIL@e71d5e connectionProperties={ClientILService=org.jboss.mq.il.uil2.UILClientILService, UIL_TCPNODELAY_KEY=yes, UIL_CHUNKSIZE_KEY=1000000, UIL_CONNECTADDRESS_KEY=null, UIL_CONNECTPORT_KEY=0, UIL_SOTIMEOUT_KEY=120000, UIL_RECEIVE_REPLIES_KEY=No, UIL_ADDRESS_KEY=10.58.33.173, UIL_PORT_KEY=8093, PingPeriod=60000, UIL_BUFFERSIZE_KEY=2048}]
      2009-06-11 10:48:30,689 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory: org.jboss.mq.SpyXAConnectionFactory@1390efd
      2009-06-11 10:48:30,689 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/-- not shown --
      2009-06-11 10:48:30,690 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
      2009-06-11 10:48:30,707 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
      2009-06-11 10:48:30,715 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
      2009-06-11 10:48:30,717 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
      2009-06-11 10:48:30,717 DEBUG [org.jboss.mq.il.uil2.UILClientILService] Starting
      2009-06-11 10:48:30,719 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created XATopicConnection: Connection@17243991[token=ConnectionToken:null/58330342c296b996c5d5b99b0e2903db rcvstate=STOPPED]
      2009-06-11 10:48:30,719 DEBUG [org.jboss.ejb3.mdb.MDB] Using client id: pinkAlerts
      2009-06-11 10:48:30,728 WARN [org.jboss.ejb3.mdb.MDB] Could not find the topic destination-jndi-name=topic/financialDocumentPost
      2009-06-11 10:48:30,731 DEBUG [org.jboss.ejb3.mdb.MDB] Initialized with config org.jboss.ejb3.mdb.MDB@1f5438
      2009-06-11 10:48:30,731 DEBUG [org.jboss.ejb3.mdb.DLQHandler] Starting DLQHandler
      2009-06-11 10:48:30,733 DEBUG [org.jboss.ejb3.mdb.DLQHandler] Started DLQHandler
      2009-06-11 10:48:30,734 INFO [org.jboss.ejb3.mdb.MDB] Reconnected to JMS provider


      Thanks
      Papiya

        • 1. Re: In Jboss Logs -

          I was finally able to resolve this by disabling the autodiscovery by adding the following row to the property attributes in the mbean declaration for application B in the destination xml file in application X -

          jnp.disableDiscovery=true