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 fo
I have the following method:
http://pastebin.com/8hHV7HxL
I'm trying to set a delay of 120 seconds to re-deliver a message to a queue.
Instead of waiting the 120 seconds it goes into the Queue immediately and is
available for dequeue. Not expected results.
I'm running 5.5-snapshot
does that co
thanks Dejan, that worked perfect :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Does-ActiveMQ-have-the-concepts-of-lazy-writes-to-disk-tp3040432p3044084.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Does ActiveMQ have something between persistent and non persistent messages?
E.g.: messages are sent to the broker's memory and are lazily written to
disk if they start to overflow memory?
Ideally the behavior I'm looking for is the speed of nonpersistent messages
but if the consumers get backed
bump, would also like to know the answer to this
--
View this message in context:
http://activemq.2283324.n4.nabble.com/overflow-messages-to-disk-tp2357768p3040327.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.