[
https://issues.apache.org/jira/browse/QPID-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081966#comment-16081966
]
Keith Wall commented on QPID-7856:
----------------------------------
That's true. The horrid {{closeWhenNoRoute}} has no meaning for AMQP 1.0 and I
hope it stays that way :). For {{sessionCountLimit}}, we realised that
putting it on Virtualhost wouldn't work for AMQP 0-8..0-10. If modifying on a
per application basis is desirable, we could always have an AMQP 1.0 specific
context var etc on VirtualHost. AMQP 1.0 would then use the VirtualHost value
if set, or otherwise fall back to the value from the Port. I do wonder
though how often this flexibility would be used.
> [Java Broker] Move broker connection related attributes into amqp port
> ----------------------------------------------------------------------
>
> Key: QPID-7856
> URL: https://issues.apache.org/jira/browse/QPID-7856
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.0
>
>
> The current implementation of broker model object interface declares
> connection related attributes "connection.sessionCountLimit",
> "connection.heartBeatDelay", "connection.closeWhenNoRoute". These attributes
> need to be moved into AMQP Port model object interface as they are only
> applicable to AMQP connections. Additionally, AMQP connection interface needs
> to expose negotiated heartbeat/idle timeouts intervals.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
