You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2017/07/11 09:05:00 UTC
[jira] [Commented] (QPID-7856) [Java Broker] Move broker connection
related attributes into amqp port
[ https://issues.apache.org/jira/browse/QPID-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081924#comment-16081924 ]
Rob Godfrey commented on QPID-7856:
-----------------------------------
Moving them to port would mean that you could not set different values for sessionCountLimit / closeWhenNoRoute / etc for different vhosts, no? Obviously this would be true anyway for 0-x protocols (where these values are exchanged before vhost selection), but for 1.0 you might want to set different limits for different vhosts.
> [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". This attributes needs 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org