Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 23 Oct 2012 19:43:12 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <713864128.17645.1351021392369.JavaMail.jiratomcat@arcas>
In-Reply-To: <1932711815.12850.1350943212386.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4123) Improve MQTT Inactivity Monitoring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482614#comment-13482614 ] 

Timothy Bish commented on AMQ-4123:
-----------------------------------

Well technically speaking you could do that on any of the transports, but hopefully that random data would generate a marshaling exception and shutdown the connection.  
                
> Improve MQTT Inactivity Monitoring
> ----------------------------------
>
>                 Key: AMQ-4123
>                 URL: https://issues.apache.org/jira/browse/AMQ-4123
>             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: http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html)
> * 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: http://www.atlassian.com/software/jira