You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Erik (JIRA)" <ji...@apache.org> on 2013/04/13 07:38:16 UTC
[jira] [Commented] (AMQ-3603) STOMP 1.1 introduced the heartBeat
header implemented by the inactivity monitor, would be nice to have this
option for stomp 1.0
[ https://issues.apache.org/jira/browse/AMQ-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630948#comment-13630948 ]
Erik commented on AMQ-3603:
---------------------------
Stomp 1.0 Heartbeat works for stomp, but not stomp+ssl.
Works:
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613?transport.defaultHeartBeat=5000,0"/>
Does not work:
<transportConnector name="stomp+ssl" uri="stomp+ssl://0.0.0.0:61613?transport.defaultHeartBeat=5000,0"/>
> STOMP 1.1 introduced the heartBeat header implemented by the inactivity monitor, would be nice to have this option for stomp 1.0
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3603
> URL: https://issues.apache.org/jira/browse/AMQ-3603
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: inactivity, monitor, stomp
> Fix For: 5.6.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira