Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-819
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dejan Bosanac
Reporter: Dave Stanley
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

Virtual destinations and wildcards

Created: 07/Feb/11 02:18 PM   Updated: 04/Mar/11 11:27 AM
Component/s: None
Affects Version/s: 5.4.2-fuse-00-00
Fix Version/s: 5.4.2-fuse-02-00

File Attachments: 1. Java Source File SingleBrokerVirtualDestinationsWithWildcardTest.java (5 kB)

Environment: Fuse MB 5.4.x

External Issue URL: https://issues.apache.org/jira/browse/AMQ-3197


 Description  « Hide
If we would like to subscribe through a virtual queue to the topic topic://test.> in theory we should subscribe to the queue queue://Consumer.a.test.>

Unfortunately this doesn't work because the queue queue://Consumer.a.test.> is not created at the subscription step.

However, if we create the queue queue://Consumer.a.test.> , for instance sending a message to it, we will have the expected virtual destination behavior.

Looking at the virtual destinations semantic, subscribing to queue://Consumer.a.test.> should create the queue queue://Consumer.a.test.>



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Dave Stanley added a comment - 07/Feb/11 02:18 PM
Attaching testcase

Dave Stanley added a comment - 08/Feb/11 10:16 AM
Tracking, comment from Dejan

It will not work at the moment. The "problem" is that when you subscribe with the wildcard consumer, no destinations will be created. And the filter that implements virtual topics only send messages to pre-existing destinations.


Dejan Bosanac added a comment - 04/Mar/11 11:27 AM
The issue is fixed and merged to fuse branch. You can test the latest (20110304.104603-14) snapshot

http://repo.fusesource.com/nexus/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.4.2-fuse-SNAPSHOT/