Forget about disconnected brokers/subscribers

[blakecmartin <bl...@gmail.com>]

I have the broker setup described here:  Problematic broker configuration
<https://stackoverflow.com/questions/49052541/why-does-this-activemq-broker-configuration-fail-after-many-brokers-are-added>  

Due to the nature of this network, brokers sometimes go offline. I can't
make any guarantee about when brokers come back online.

I'm seeing the following warning: *TopicSubscription: consumer=ID:[...]: has
twice its prefetch limit pending, without an ack; it appears to be slow*

What I believe is happening is that messages destined for subscribers on the
disconnected part of the network (i.e., on the other LAN) get spooled
indefinitely. This eventually causes an OutOfMemoryError on one of the
brokers (not a catastrophe because the broker isn't embedded in the
application).

I'd like my messages to be "fire and forget". If a remote subscriber is
unreachable because one of the brokers is offline, drop the message. It'd be
even better if I could forget the remote subscriber exists after a short
time.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

[SOLVED] Re: Forget about disconnected brokers/subscribers

[Blake Martin <bl...@gmail.com>]

It turned out there's a configuration setting on the broker that causes it to
timeout remote durable subscribers:

I'm not creating any durable subscribers in my application code, but it
appears that when you use a broker as a network bridge it creates durable
subscriptions on behalf of the topic subscribers that are connected to it,
even if they're remote subscribers.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html