You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/07/11 12:48:00 UTC
[jira] [Commented] (QPID-7856) [Java Broker] Convert broker
connection related attributes into context variables and expose them on
amqp port as derived attributes
[ https://issues.apache.org/jira/browse/QPID-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082154#comment-16082154 ]
Keith Wall commented on QPID-7856:
----------------------------------
I agree that having a method to influence these settings on a per user (or group) basis would be ideal, but that is not an option we have at the moment. I can foresee having the flexibility to have different {{sessionCountLimit}} in force within a single Broker would be useful - especially when porting large applications between Qpid JMS Clients. I think, pragmatically, Port is best home we have at the moment. It will be one of our standard pattern context variable+derived attribute, so the ability to override at a global level is maintained. I am happy to add the ability to override for AMQP 1.0 at a virtualhost level if you think this valuable.
> [Java Broker] Convert broker connection related attributes into context variables and expose them on amqp port as derived attributes
> ------------------------------------------------------------------------------------------------------------------------------------
>
> 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 converted into context variables and exposed on AMQP Port as derived attributes, 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