[
https://issues.apache.org/jira/browse/QPID-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618105#comment-13618105
]
Robbie Gemmell commented on QPID-4677:
--------------------------------------
One of the changes is actually a fix for an earlier JIRA (QPID-4661) so I have
commented on it to that effect, leaving the following commits for this JIRA:
http://svn.apache.org/r1462471
http://svn.apache.org/r1462472
http://svn.apache.org/r1462550
> [Java Broker] fix incorrect attribute names, group inheritable defaults and
> add missing ones
> --------------------------------------------------------------------------------------------
>
> Key: QPID-4677
> URL: https://issues.apache.org/jira/browse/QPID-4677
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.21, 0.22
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.23
>
>
> The introduction of the new broker level configuration store has exposed some
> issues with the attribute on the Broker, VirtualHost, Queue, Connection etc
> objects.
> There is a naming mismatch between some of the the alert threshold attributes
> on the Queue and the inheritable defaults for those values defined at the
> VirtualHost and Broker level. These names need to be reconciled.
> The attribute names of the inheritable defaults do not lend themselves to
> clarity as to which attributes affect the Broker, VirtualHost etc directly
> and those which are instead intended as inheritable defaults for children
> objects such as VirtualHosts, Connections, Queues etc. The attribute names
> should be prefixed with the object type to group them and clarify their
> influence.
> Finally, there is currently no way to configure the store TransactionTimeout
> functionality at the broker-wide level, so desire to use this functionality
> would force users into using the now otherwise optional virtualhost XML
> configuration files. Inheritable defaults should be added to the Broker for
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
