You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2013/02/14 19:57:17 UTC
[jira] [Updated] (AMQ-4320) Destinations are not auto created when
using Composite Destination configured on the broker
[ https://issues.apache.org/jira/browse/AMQ-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated AMQ-4320:
-------------------------------
Description:
When using a composite destination as defined below, the destination are not auto created:
{code}
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<compositeQueue name="MY.QUEUE">
<forwardTo>
<queue physicalName="FOO" />
<topic physicalName="BAR" />
</forwardTo>
</compositeTopic>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>
{code}
The destinations FOO and BAR are not created if they do not exist and the messages are dropped.
Current work around is to define startup destinations as shown below or ensure the destinations are created by consumers prior to sending messages to the composite destination.
{code}
<destinations>
<queue physicalName="FOO" />
<topic physicalName="BAR" />
</destinations>
{code}
> Destinations are not auto created when using Composite Destination configured on the broker
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-4320
> URL: https://issues.apache.org/jira/browse/AMQ-4320
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Hiram Chirino
>
> When using a composite destination as defined below, the destination are not auto created:
> {code}
> <destinationInterceptors>
> <virtualDestinationInterceptor>
> <virtualDestinations>
> <compositeQueue name="MY.QUEUE">
> <forwardTo>
> <queue physicalName="FOO" />
> <topic physicalName="BAR" />
> </forwardTo>
> </compositeTopic>
> </virtualDestinations>
> </virtualDestinationInterceptor>
> </destinationInterceptors>
> {code}
> The destinations FOO and BAR are not created if they do not exist and the messages are dropped.
> Current work around is to define startup destinations as shown below or ensure the destinations are created by consumers prior to sending messages to the composite destination.
> {code}
> <destinations>
> <queue physicalName="FOO" />
> <topic physicalName="BAR" />
> </destinations>
> {code}
--
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