Three things come to mind: 1) sendFailIfNoSpace in the system usage configuration for the broker 2) sendTimeout on the connection factory or ?jms.sendTimeout 3) If using failover: configure maxReconnectAttempts such that it won't block for ever trying to reconnect if the broker goes away.
On 16 February 2011 19:13, devnull <[email protected]> wrote: > > I'm using ActiveMQ in Java to log incoming analytics beacons. Ideally if > the > queue goes down or gets locked up I'd like to fail as fast as possible, log > the beacon locally then return to the client without hanging, then try to > reconnect later. > > What is the best connection URI and URI parameters for that use case when > using ActiveMQ? > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/What-is-the-best-connection-URI-for-ActiveMQ-if-I-want-to-Fail-Fast-tp3309543p3309543.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
