The advisories are very interesting and custom; they are not regular Topics. For example, creating a consumer on one broker in a network of brokers may or may not result in a consumer advisory on other brokers depending on things like the conduitSubscriptions setting.
Using an application-specific Topic is a good way to go for event notifications like this. BTW - on the "producer doesn't get created on the target destination" comment - perhaps I should have said, "the producer is never registered as a producer on the target destination". The producer is created, and it sends a message to the target destination, but it is not "associated with" the target destination. Since the producer-creation advisories are destination-specific, that makes it hard to send a producer creation advisory, which would only be feasible at send-time since that's the first time the destination is known. This is one of those finer points of JMS - consumers must be tied to destinations all the time, but producers can decide a destination on every message send. -- View this message in context: http://activemq.2283324.n4.nabble.com/Sending-directly-to-a-queue-doesn-t-raise-ActiveMQ-Advisory-Producer-Queue-tp4690888p4691303.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
