activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-398) AMQP protocol idle timeout issue
Date Mon, 15 Feb 2016 16:40:18 GMT

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

ASF GitHub Bot commented on ARTEMIS-398:
----------------------------------------

Github user gemmellr commented on the pull request:

    https://github.com/apache/activemq-artemis/pull/390#issuecomment-184291017
  
    I'd suggest deriving the 'now' ms value passed to Transport#tick() from System#nanoTime()
rather than using System#currentTimeInMillis(), since the latter is subject to wall clock
change that can throw things off. Similar change made in https://issues.apache.org/jira/browse/AMQ-6031


> AMQP protocol idle timeout issue
> --------------------------------
>
>                 Key: ARTEMIS-398
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-398
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>            Reporter: Andy Taylor
>            Assignee: Andy Taylor
>
> Basically we only tick once where we should keep ticking every n seconds



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message