-
Bug
-
Resolution: Done
-
Major
-
7.1.0.fuse-046
-
None
When using a composite destination as defined below, the destination are not auto created:| <destinationInterceptors>|
<virtualDestinationInterceptor> |
<virtualDestinations> |
<compositeQueue name="MY.QUEUE"> |
<forwardTo> |
<queue physicalName="FOO" /> |
<topic physicalName="BAR" /> |
</forwardTo> |
</compositeTopic> |
</virtualDestinations> |
</virtualDestinationInterceptor> |
</destinationInterceptors> |
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.| <destinations>|
<queue physicalName="FOO" /> |
<topic physicalName="BAR" /> |
</destinations> |
- relates to
-
ENTMQ-502 Virutal Destination is not auto created when using Composite Destination
- Closed