Hi Michael
This behaviour is correct according to the STOMP 1.2 specification [1]: Both
the client and the server do only state what they are able to do (first
unsigned int) and what they would like the remote to do (second unsigned int).
The actual heart-beating is then determined based on the
Hello,
with STOMP 1.2, the current version 1.6 of the Apollo seems to use
default heart-beat intervals of 100 and 1000 (outgoing/incoming).
So even if the client informs that heart-beating is not supported by the
client library, the server seems to expect heart-beating in both directions.
S
