Re: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

Yes, the address-settings will apply the values during creation... Glad it worked out... Notice there's a scan done to delete the queues... i dealt at some point with a customer that had reconnects, and having a fast reconnect had issues with auto-delete.. for that reason we changed it to scan..

Re: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

What version you’re using ? I will do some checking and get back to you. On Tue, Sep 27, 2022 at 1:29 PM John Lilley wrote: > No consumer, no producers, no messages. > > > > > [image: rg] > > John Lilley > > Chief Architect, Redpoint Global Inc. > > 888 Worces

RE: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

We finally figured out what it is. The auto-delete settings from broker.xml persist in the queue attributes even after you change broker.xml. Since the default for a new broker comes up “auto-delete false”, my tests created some queues that had that attributes, and even after I changed broker.xm

RE: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

Justin, Thanks for your reply. The situation is rather odd. I have a colleague who can run Artemis on either his Linux or Windows VM, and in either case the auto-delete happens just fine, using the same test situation. This isn’t an especially complex use case. The app comes up, uses JMS to

Re: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

Did a consumer connect to the queue at any point? The broker will wait for at least one consumer to connect so that it doesn't delete a queue before it's actually used. Justin On Tue, Sep 27, 2022 at 12:30 PM John Lilley wrote: > No consumer, no producers, no messages. > > > > > [image: rg]

RE: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

No consumer, no producers, no messages. [rg] John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: Clebert Suconi

Re: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

No consumers ? On Tue, Sep 27, 2022 at 10:34 AM John Lilley wrote: > The queues are all empty. > > Thanks > > john > > > > > [image: rg] > > John Lilley > > Chief Architect, Redpoint Global Inc. > > 888 Worcester Street, Suite 200 Wellesley, MA 02482 >

RE: Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

The queues are all empty. Thanks john [rg] John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: herbert.helmstr.

Antwort: [Ext] RE: Help getting Artemis to auto-delete empty/idle queues

Hi John, did you check TimeToLive of the Messages in the queue? At least for me this was the problem for a similar case. Herbert Von:"John Lilley" An: "users@activemq.apache.org" Datum: 27.09.2022 14:40 Betreff:[Ext] RE: Help getting Artemis to auto-delete empty/idle queu

Re: ActiveMQ client support for JMS 3.0

Right now, there has not been a formal discussion about jakarta client. Please stay tuned— there is definitely interest in making that happen. Thanks, Matt > On Sep 25, 2022, at 2:59 PM, Andrés Torres García wrote: > > Understood Matt, right now we don't use the new API methods, what we are >

RE: Help getting Artemis to auto-delete empty/idle queues

Thanks http://www.w3.org/2001/XMLSchema-instance xmlns:xi=http://www.w3.org/2001/XInclude xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation="urn:activemq:core "> lo

RE: Help getting Artemis to auto-delete empty/idle queues

Thanks [rg] John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: Justin Bertram Sent: Monday, September 26, 202

Re: ActiveMQ client support for JMS 3.0

We've been trying to get an ActiveMQ client build using the new jakarta classes, we had been playing with shading Active MQ (byte code update of imports) inspired by https://github.com/apache/tomcat-jakartaee-migration, we could maybe use this while we wait for the official 3.0 support, we are just