You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2014/08/28 14:08:08 UTC

[jira] [Assigned] (AMQ-5305) runtime configuration - allow changes to configuration elements

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

Dejan Bosanac reassigned AMQ-5305:
----------------------------------

    Assignee: Dejan Bosanac

> 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
>            Assignee: Dejan Bosanac
>            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)