Sam Wilkinson created AMQ-5305:
----------------------------------
Summary: runtime configuration - allow changes to <destinations>
configuration elements
Key: AMQ-5305
URL: https://issues.apache.org/jira/browse/AMQ-5305
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.10.0
Reporter: Sam Wilkinson
Priority: Minor
Extend the runtime configuration feature (AMQ-4682) to allow changes to the
<destinations> configuration element.
As of 5.10.0 if you create a compositeTopic with queues/topics or filtered
destinations within the
<destinationInterceptors><virtualDestinationInterceptor><virtualDestinations>
element the CompositeTopic will not showup in the Broker Manager Topics page.
{code:xml}
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<!-- Add this compositeTopic after
ActiveMQ start -->
<compositeTopic name="CompositeTopic"
forwardOnly="false">
<forwardTo>
<queue
physicalName="ForwardedQueue" />
</forwardTo>
</compositeTopic>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>
<destinations>
<!-- CompositeTopic and ForwardedQueue queue will not
showup in the Broker Manager unless these are defined (or someone sends a
message to the CompositeTopic. -->
<!--<topic physicalName="CompositeTopic" />-->
<!--<queue physicalName="ForwardedQueue" />-->
</destinations>
{code}
Note: This is more just a usability/management improvement.
The broker does correctly forward messages to the ForwardedQueue, if it is not
defined in the <destinations> element.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
