[
https://issues.apache.org/jira/browse/ARTEMIS-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic updated ARTEMIS-1924:
-------------------------------------
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.
Priority: Blocker (was: Major)
Issue Type: Bug (was: Improvement)
Summary: AMQP Idle Timeout Configuration is Messed up (was: Adding the
possibility of configure AMQP IdleTimeout)
> AMQP Idle Timeout Configuration is Messed up
> --------------------------------------------
>
> 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)
