Purge just discards messages, which is likely sufficient for your case.
Although it sometimes does not delete messages - perhaps those that are
in-flight?
For unit tests, creating a fresh broker instance each time using
BrokerService eliminates the risk of side-effects from prior runs.
--
View
What’s the best way to delete all queues and messages in those queues.
Basically, I want a fresh broker, it’s unclear whether purge() in the JMS
just empties the queue or whether it also removes the queue too.
--
Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.word
Gary,
I was able to get failover working between brokers in a network of brokers
using the maxReconnectAttempts=0 URI option. However, when I tried adding
priorityBackup=true, I ran into problems.
http://activemq.2283324.n4.nabble.com/priorityBackup-not-supported-with-masterslave-td4677626.html#a
thanks for closing the loop :-)
On 23 October 2014 23:01, Alistair Young wrote:
> turned out a 3rd party jar in the lib directory was still compiled against
> 5.8.0. Compiling it against 5.10.0 solved the problem.
>
> Thanks,
>
> Alistair
>
> -
> mov eax,1
> mov ebx,0
> int 80
>
Hi
The source code for hawtio is at github. The activemq plugin is at
https://github.com/hawtio/hawtio/tree/master/hawtio-web/src/main/webapp/app/activemq
Work is ongoing on hawtio to add role based security in the ui as
well, eg so only admin users can see the create queue button etc.
Though its
