I have the same problem: if one don't want the broker A to block at startup if a remote broker B is not reachable, the "startupMaxReconnectAttempts" parameter must be used, but A won't try to connect to B anymore, so all messages will be queued in A until it's restarted. Is there any workaround? -- View this message in context: http://activemq.2283324.n4.nabble.com/broker-config-if-destination-may-be-down-tp3086163p3209402.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
- broker config if destination may be down logosdev
- Re: broker config if destination may be down Dejan Bosanac
- Re: broker config if destination may be down logosdev
- Re: broker config if destination may be down logosdev
- Re: broker config if destination may be dow... Dejan Bosanac
- Re: broker config if destination may b... logosdev
- Re: broker config if destination m... Miguel
