You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Murat ÖZDEMİR (JIRA)" <ji...@apache.org> on 2012/11/16 11:04:12 UTC

[jira] [Comment Edited] (AMQ-4117) MQTT Inactivity Monitor doesn't respect client keep alive setting.

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

Murat ÖZDEMİR edited comment on AMQ-4117 at 11/16/12 10:03 AM:
---------------------------------------------------------------

Despite sending PINGREQ from client by 10 seconds interval, broker still disconnects client after default keepAlive time. (Using v.5.7.0)
                
      was (Author: mozdemir):
    Despite sending PINGREQ from client by 10 seconds interval, broker still disconnects client after default keepAlive time. (Using v.5.6.0)
                  
> MQTT Inactivity Monitor doesn't respect client keep alive setting.
> ------------------------------------------------------------------
>
>                 Key: AMQ-4117
>                 URL: https://issues.apache.org/jira/browse/AMQ-4117
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.7.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 5.8.0
>
>
> The MQTT Inactivity Monitor starts its monitoring thread to early which means that it cannot honor the keepAlive time sent by the client.  The transport should wait until its received the client CONNECT command before it starts its monitoring thread. 

--
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