Stomp 1.0 does not provide for an inactivity monitor. A client connect that stays idle will remain active on the broker indefinitely. With 1.1, the inactivity monitor has come into play in response to the heartBeat header. For 1.0 clients we need a way to indicate that there is a default heartBeat header, so a broker readTimeout and no expectation of a writeTimeout.
Providing a transport option for stomp like stomp://0.0.0.0:0?transport.defaultHeartBeat=5000,0 would be nice. In the absence of a heartbeat header, as in the stomp 1.0 case, this default value would cause an InactivityMonitor with readCheck of 500 to be installed on each new broker stomp transport connection.
Any client that remains inactive for more than 5 seconds will have their broker connection closed.