Try adding a 'staticallyIncludedDestinations' element. Like
<networkConnector .... >
<staticallyIncludedDestinations>
<queue physicalName="always.include.queue"/>
</staticallyIncludedDestinations>
</networkConnector>
That should cause the 'always.include.queue' queue to always be forwarded.
On Fri, Sep 20, 2013 at 3:04 AM, michael.mathieu <[email protected]> wrote:
> Hi all!
>
> I posted last week a message on stackoverflow, but I received no answers,
> maybe I'd have more chance here.
>
> As it's clearly explained here :
> http://blog.garytully.com/2012/07/activemq-broker-networks-think-demand.html
> When there's no consumer for the destination queue, the messages are no
> longer forwarded. Is there a way to force the forward? Could be interesting
> to avoid that messages stay in the local queue (e.g. a VM in a cloud: we
> would like to force the forward of the messages and then shutdown the VM,
> even if no consumer at the destination).
>
> Thanks for your answers!
>
> (origin:
> http://stackoverflow.com/questions/18751617/activemq-network-broker-force-forward-if-no-consumer-at-the-destination)
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Network-broker-force-forward-if-no-consumer-at-destination-tp4671687.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Hiram Chirino
Engineering | Red Hat, Inc.
[email protected] | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
