You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/19 21:45:00 UTC

[jira] [Commented] (ARTEMIS-1924) Adding the ability to configure the AMQP IdleTimeout

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

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

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2149

    ARTEMIS-1924 Test consumer cleanup after socket connection reset

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1924

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2149.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2149
    
----
commit e0f28e8471fd1306b4455c285e9561339303127a
Author: Clebert Suconic <cl...@...>
Date:   2018-06-19T21:42:46Z

    ARTEMIS-1924 Test consumer cleanup after socket connection reset

----


>  Adding the ability to configure the AMQP IdleTimeout 
> ------------------------------------------------------
>
>                 Key: ARTEMIS-1924
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1924
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>         Environment: There is no way to proper configure AMQP. The only way is through a server wide property which would break clustering and make the server broken on clustering.
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Blocker
>             Fix For: 2.7.0, 2.6.3
>
>
> connection Timeout Override was meant to bypass client behavior on core protocol, not to specify the TTL on AMQP connections or server based protocols.
>  
> the server will send a TTL to the client, so it should be possible to pass 0 and disable TTL.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)