activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4162) Provide JMX visibility into options applied via destination name query parameters
Date Tue, 06 Nov 2012 16:50:12 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-4162.
-----------------------------

    Resolution: Fixed
      Assignee: Gary Tully

in http://svn.apache.org/viewvc?rev=1406210&view=rev

options now exposed by destinationView, queues and topics
                
> Provide JMX visibility into options applied via destination name query parameters
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-4162
>                 URL: https://issues.apache.org/jira/browse/AMQ-4162
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, JMX
>    Affects Versions: 5.7.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: destinations, jmx, metadata
>             Fix For: 5.8.0
>
>
> Users would like to be able to add meta information to a destination, such as the owner
of a queue.
> Destination options allow arbitrary information to be associated with a destination via
a query parameter on the name.
> They are normally hidden b/c they are interpreted internally as policy entry overrides
so not generally of interest.
> Providing visibility of this information makes it usable for meta info purposes b/c a
user can add any information they like in there.
> {code}
>  <broker ...>
>    <destinations>
>      <queue physicalName="FOO.BAR?owner=joe&mobile=123" />
>    </destinations>
>  </broker>{code}
> via JMX the query string is available in the DestinationView via the options attribute.
> Changing this information over time does not effect the destination.

--
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

Mime
View raw message