activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Murat ÖZDEMİR (JIRA) <j...@apache.org>
Subject [jira] [Commented] (AMQ-4117) MQTT Inactivity Monitor doesn't respect client keep alive setting.
Date Fri, 16 Nov 2012 10:02:13 GMT

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

Murat ÖZDEMİR commented on AMQ-4117:
------------------------------------

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

Mime
View raw message