Delete durable queue

2023-11-30 Thread KOROTKOVA Anna
Good day I use spring-boot-starter-artemis for my application. I create durable queues, but every time after consuming Artemis trying to delete durable queue. I would like to know how to fix it on client site. Now I get permission for artemis user only send and consume, without deleting. But

Re: ActiveMQ classic - no persistence but need lease-database-locker

2023-11-30 Thread Martin Lichtin
Yes, that's what I currently need to do, keep the store. But to avoid accidentally using it, I really would want to disable it. https://issues.apache.org/jira/browse/AMQ-9410 Thx, On 29/11/2023 16:27, Jean-Baptiste Onofré wrote: That's not currently possible as the lease depends on the store

Re: strange behavior with ActiveMQ, Wildfly and Apache Camel client...

2023-11-30 Thread Justin Bertram
I'm not aware of any false positives for the invalid concurrent session usage check. The stack-trace indicates the offense is occurring in the thread used to service an invocation of a MessageListener's onMessage method. Presumably there is another thread using the same Session. Do you have a way

Re: deleted Artemis diverts return after restart

2023-11-30 Thread Justin Bertram
I went ahead and created ARTEMIS-4521 [1] for the divert issue and sent a PR. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-4521 On Thu, Nov 30, 2023 at 12:01 PM Justin Bertram wrote: > This is a bug. The createDivert operation stores the divert configuration > in the journal, but

Re: deleted Artemis diverts return after restart

2023-11-30 Thread Justin Bertram
This is a bug. The createDivert operation stores the divert configuration in the journal, but the destroyDivert operation doesn't delete it. Therefore, when the broker restarts it reads the divert configuration from the journal and deploys it. Please open a Jira. Thanks! Also, if you're needing

strange behavior with ActiveMQ, Wildfly and Apache Camel client...

2023-11-30 Thread Zoltan Lutor (Nokia)
Hi, I've experienced some strange behavior during trying to experiment with Apache Camel 4.0 SJMS2 and Wildfly 29.0.1-1 and Apache ActiveMQ Artemis: 1. AMQ212051: Invalid concurrent session usage. Sessions are not supposed to be used by more than one thread concurrently. java.lang.Exception:

Re: Artemis management console refresh rate

2023-11-30 Thread Domenico Francesco Bruscino
Hi Aleksandr, the default rate value of 5 seconds is hard coded in the hawtio console, see https://github.com/hawtio/hawtio-integration/blob/v5.2.0/plugins/jmx/ts/workspace.ts#L63 Regards, Domenico On Thu, 30 Nov 2023 at 10:56, MILOVIDOV Aleksandr wrote: > Hi Team, > > In the management

deleted Artemis diverts return after restart

2023-11-30 Thread Dondorp, Erwin
Classification: Public Hello, After a JMX createDivert, followed by a JMX destroyDivert, followed by a broker restart, the divert is visible again. I noticed this behavior when trying to delete the diverts from retro-active addresses. But the above scenario is the simplest case and makes it

Artemis management console refresh rate

2023-11-30 Thread MILOVIDOV Aleksandr
Hi Team, In the management console of ActiveMQ Artemis any user can change preferences and set update rate in Jolokia settings. Default update rate is 5 seconds. When application creates or deletes temporary queues too frequently, it is difficult to work in the console. This setting is applied