Stomp clients disconnected due to not receiving data

[peterparker]

Hi.

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,

Christopher

[ataylor]

what stomp version is the PHP PEAR library using, I know keep alive is only in 1.1 not 1.0, maybe there is a version mis match, altho we do support both protocols

[peterparker]

Hi and thank you for your answer.

I did not find the information about what stomp protocol is supported from the PHP module since it is rather poorly documented...

I'd expect it to be Stomp 1.0. But since it is a text protocol I am sure I can implement everything we need to simply transmit such a message manually.

If you say HornetQ supports stomp 1.1 you are probably referring to HornetQ 2.2.14, aren't you? I did not find in the documentation where it explicitly says whether 1.0 or 1.1 are supported in 2.2.5 or 2.2.14 (http://docs.jboss.org/hornetq/2.2.5.Final/user-manual/en/html/interoperability.html#stomp, http://docs.jboss.org/hornetq/2.2.14.Final/user-manual/en/html/interoperability.html#stomp)...

Unfortunately, we cannot use 2.2.14 right now since it is not stable for us (see here: https://community.jboss.org/thread/200606).

For 2.2.5:

The STOMP 1.1 protocol (http://stomp.github.com/stomp-specification-1.1.html) defines that if a sender does not have a proper stomp frame to send (what would be the case for a mere consumer) it should send single newline byte (0x0A) instead of a heart-beat. Would this work? Does this generate a stomp frame that is maintained as a message in the Queue? or can we just send this newline character every 15 seconds and the connection will stay alive?

Thank you for your time,

Christopher