Hi JB, Thanks for your reply.
Yes, I am using "lock", so it should work as you mentioned. Now, temporarily I have the Slave down (not running); would this affect Purging a Queue with the Web-Console on the Master node ? Perhaps, to Purge Queues in this scenario, both Master and Slave need to be running, would this be the case ? -----Original Message----- From: Jean-Baptiste Onofré <j...@nanthrax.net> Sent: Wednesday, June 22, 2022 12:45 AM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.15.8 fail over cluster - web console - purging a queue Hi Francisco Just to be clear: are you using master/slave via lock or network of brokers with masterslave URL ? I'm sure master/slave lock works (I'm using it :)). So I guess you are using NoB with masterslave URL. Regards JB On Wed, Jun 22, 2022 at 12:01 AM MENDEZ Francisco <francisco.men...@thalesgroup.com.invalid> wrote: > > Hello, > > When using ActiveMQ standalone installation, I am able to purge a queue or > delete a message from queue using the web console; But when configuring > ActiveMQ as Fail Over cluster (using two nodes - master and slave > configuration); when attempting to purge a queue through the web console; I > get a message that an exception happens and the purge did not work. > > Looking at the activemq log file, there is a > java.lang.UnsupportedOperationException ? > > does anyone know about this? > I wonder if this is related to user permissions, but using the admin account, > I still got the same error I mentioned above. > > or is this related to the master/slave fail over configuration? (note: at > this time only the master node is running, do I need to have the slave node > running as well when purging a queue ? ) > > > Thanks in advance for any help/feedback.
