2 Replies Latest reply on Jun 4, 2012 8:59 AM by peterparker

    Stomp clients disconnected due to not receiving data

    peterparker Newbie


      We have the following error messages in our HornetQ log files:

      * [hornetq-failure-check-thread] 4-Jun 9:26:32,843 WARNING [StompConnection]  Connection failure has been detected: Did not receive data from /xxx.xx.xx.xx:38062. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=3]

      * [hornetq-failure-check-thread] 4-Jun 9:26:32,843 WARNING [ServerSessionImpl]  Client connection failed, clearing up resources for session 88ef67da-ae16-11e1-baab-e92ad3c301f4


      The message gets repeated every 30 seconds (corresponds to client-failure-check setting) tested in both version 2.2.5 and 2.2.14.


      We are using the PHP PEAR library for stomp connecting to the MQ and needed to handle connection abort exceptions in our consumer code to reconnect on these forced disconnects.



      My understanding, from reading around, is, that the MQ expects the connected client to "send" data to the queue.


      But I have some questions regarding this:

      1. The connected client is a consumer that actively consumes a couple of hundred messages within the 30 seconds it is connected. Why does the HornetQ think it is not doing anything?
      2. If we have to send a message, how should this be implemented? AFAIK the current HornetQ version does not support a "Ping" message that could be used to send a heartbeat signal from the consumer to the queue, so what is the correct approach to choose here?


      Thank you,