0 Replies Latest reply on Aug 7, 2008 2:41 PM by kevin m

    "No pong received" every 60 seconds, forever

    kevin m Newbie

      [OK, I guess my previous post is a "bad post" (Me too, or similar problem.) Hopefully this is a good post. Unless it's rejected for being a duplicate.]

      The server is 4.0.3SP1 jboss server on a linux box. The client is 4.0.2.

      We are experiencing a problem similar to the one mentioned in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67532. From that post, it was unclear if there was a JBoss problem behind the problem. My question is, is there, and has it been fixed?

      Our JMS client has a topic connection that has a listener. The listener sets a flag, and another thread will [very quickly] clean up and then reconnect when it sees the flag set.

      The problems began when there was a network outage.

      Since then, we've been in a cycling loop of reconnects. The client gets a "no pong received". The onException is invoked. The thread cleans up and reconnects. Messages are transferred from the client to the server, and from the server to the client. A minute later, we get a "no pong received" exception - repeat.

      2008-08-06 09:46:01,416 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
      2008-08-06 09:46:02,112 WARN [TopicConnectionManager] successfully established a connection to the management server
      2008-08-06 09:47:01,416 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
      2008-08-06 09:47:02,459 WARN [TopicConnectionManager] successfully established a connection to the management server
      2008-08-06 09:48:01,420 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
      2008-08-06 09:48:01,811 WARN [TopicConnectionManager] successfully established a connection to the management server
      2008-08-06 09:49:01,424 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
      2008-08-06 09:49:02,152 WARN [TopicConnectionManager] successfully established a connection to the management server
      2008-08-06 09:50:01,424 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
      2008-08-06 09:50:01,500 WARN [TopicConnectionManager] successfully established a connection to the management server
      2008-08-06 09:51:01,428 WARN [TopicConnectionManager] the connection to the management server was broken: org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)


      Here's what our debug log shows. (We don't have a jboss.mq trace.)

      2008-08-06 10:20:01,476 DEBUG [TopicConnectionManager] exception reported on topic connection
      org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
       at org.jboss.mq.Connection$PingTask.run(Connection.java:1323)
       at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
       at java.lang.Thread.run(Thread.java:619)
      Caused by: java.io.IOException: ping timeout.
       ... 3 more


      We have seen the same exact problem on many clients on different machines, connected to the same server. Apparently, the same network outage affected them all, and put them all into the same state.

      There are no huge messages, or large numbers of exceptions. This is verified with tcpdump.

      Since JMS seems like its otherwise working - server sees what the client published, client sees what the server published - this looks like some sort of JBoss issue.

      Can anyone help? I'm not sure what else it would be helpful to know.