1 Reply Latest reply on Jul 1, 2002 6:08 AM by slz1972

    pinging ponging

    vishalsant

      hi ,
      i have a jboss insatnce that is running under a wee
      bit of stress .A big ear file with some 10 ejbs and 5 war files etc ....
      the more the bulk of the ar file increases the more jboss
      has a problem ...
      I start getting

      java.io.IOException: ping timeout.
      at org.jboss.mq.Connection$PingTask.run(Connection.java:905)
      at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
      at java.lang.Thread.run(Thread.java:479)
      org.jboss.mq.SpyJMSException: Connection Failed
      at org.jboss.mq.Connection.asynchFailure(Connection.java:466)
      at org.jboss.mq.Connection$PingTask.run(Connection.java:912)
      at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
      at java.lang.Thread.run(Thread.java:479)
      linked exception is:
      java.io.IOException: ping timeout.
      at org.jboss.mq.Connection$PingTask.run(Connection.java:905)
      at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
      at java.lang.Thread.run(Thread.java:479)


      could anyone shed a light on this intrenal message i keep
      on recieving

      vishal

        • 1. Re: pinging ponging
          slz1972

          The situation might happen when:
          1. your JBoss/JBossMQ server has restarted, and
          2. your JBossMQ client program doesn't close the old connection (queue/topic).

          basically, a PingTask thread is started when a connection is started. And it will start to complain about lost server connection once the server is restarted. The only way to get rid of it is to call Connection::close()

          hope that helps,
          sheng