Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-175

Destinations are no auto created when using Composite Destination configured on the broker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBoss A-MQ 6.0
    • 7.1.0.fuse-046
    • broker
    • 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>

            hchirino Hiram Chirino
            rhn-support-jsherman Jason Sherman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: