I'm not convinced this is a bug. The advisory is for the creation of producers. In this use of a producer, it doesn't get created on the target destination - ever, so no creation advisory.
If a change is made so that the broker sends the producer-added advisory, it will be immediately followed by a producer-removed advisory. That means every message sent by a producer to destinations, other than the one for which it was originally created, will include 2 advisory messages. That's a lot of overhead. -- View this message in context: http://activemq.2283324.n4.nabble.com/Sending-directly-to-a-queue-doesn-t-raise-ActiveMQ-Advisory-Producer-Queue-tp4690888p4690946.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
