activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Posta (JIRA)" <>
Subject [jira] [Commented] (AMQ-4123) Improve MQTT Inactivity Monitoring
Date Tue, 23 Oct 2012 19:25:12 GMT


Christian Posta commented on AMQ-4123:

I considered that too. However, the PINGREQ/PINGRESP are frames that are part of the contract/spec
that determine whether a connection should stay open (insofar as I understand). So if the
PINGREQ frame isn't treated specifically in the InactivityMonitor, then it's only counting
whether or not more data has come in over the wire. But in that case, you could just send
in random data not related to the MQTT spec and that alone would keep the InactivityMonitor
alive... Which isn't necessarily desired? 
> Improve MQTT Inactivity Monitoring
> ----------------------------------
>                 Key: AMQ-4123
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT, Transport
>    Affects Versions: 5.7.0
>            Reporter: Christian Posta
>            Priority: Minor
>             Fix For: 5.8.0
> * Keep Alive should be 1.5 * the keep alive value specified by client (the grace period
described in spec:
> * MQTTInactivityMonitor checking for KeepAliveInfo in the onCommand, but it can never
get a KeepAliveInfo as it is
> * What to do when user explicitly turns Inactivity Monitor off?
> * Should there be defaults to close potentially dead connections?

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:

View raw message