Yes, sorry I replied to the wrong thread.

--
    Vilius

From: John Lilley <john.lil...@redpointglobal.com.INVALID>
Sent: Friday, November 4, 2022 2:34 PM
To: users@activemq.apache.org
Subject: RE: Problem with Artemis auto-delete queues

Vilius,

Unless someone has a solution to this (apparent) bug, we will probably do a 
similar manual cleanup sweep.  Although I’d like to use a management API.  
Currently looking into the message-based interface.

Thanks
john



[rg]<https://www.redpointglobal.com/>

John Lilley

Data Management Chief Architect, Redpoint Global Inc.

888 Worcester Street, Suite 200 Wellesley, MA 02482

M: +1 7209385761<tel:+1%207209385761> | 
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
From: Vilius Šumskas <vilius.sums...@rivile.lt<mailto:vilius.sums...@rivile.lt>>
Sent: Friday, November 4, 2022 12:24 AM
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: RE: Problem with Artemis auto-delete queues

*** [Caution] This email is from an external source. Please use caution 
responding, opening attachments or clicking embedded links. ***

Hi,

we needed similar cleanup being made on our testing environment, but to keep 
data folder, so we have used this script:

/var/lib/artemis/bin/artemis address show --url tcp://localhost:61616 --user 
admin --password adminpassword > addresses.txt
while read -r queue; do ./artemis queue delete --name $queue --url 
tcp://localhost:61616 --user admin --password adminpassword; done < 
addresses.txt
while read -r address; do ./artemis address delete --name $address --url 
tcp://localhost:61616 --user admin --password adminpassword; done < 
addresses.txt

This works for us because we have 1:1 mapping of addresses and queues. It 
gathers all address list, then sends everything to artemis CLI to delete queues 
first, then addresses themselves.

Hope this helps.

--
    Vilius

From: John Lilley 
<john.lil...@redpointglobal.com.INVALID<mailto:john.lil...@redpointglobal.com.INVALID>>
Sent: Thursday, November 3, 2022 6:45 PM
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: RE: Problem with Artemis auto-delete queues

Hi Justin,

My dependency is

<dependency>
    <groupId>org.apache.activemq</groupId>
    <artifactId>artemis-jms-client-all</artifactId>
    <version>2.26.0</version>
</dependency>

The artemis server I am running is 2-24.0

OS is Windows.

Thanks
John



[rg]<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.redpointglobal.com%2f&c=E,1,88RSDFty6yi5Wu_eqSt8B5ocbaOslLNuF1yrbhosXCUDKcWABHsujkJftmSy4u2ZvHojfF5ot2b5Q_ZZBO_Uzra42-csvyC6BwRSZ3oZ2ZfLhwmM&typo=1>

John Lilley

Data Management Chief Architect, Redpoint Global Inc.

888 Worcester Street, Suite 200 Wellesley, MA 02482

M: +1 7209385761<tel:+1%207209385761> | 
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
From: Justin Bertram <jbert...@apache.org<mailto:jbert...@apache.org>>
Sent: Thursday, November 3, 2022 9:21 AM
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: Re: Problem with Artemis auto-delete queues

*** [Caution] This email is from an external source. Please use caution 
responding, opening attachments or clicking embedded links. ***

Which JMS client are you using?


Justin


On Tue, Nov 1, 2022 at 7:58 PM John Lilley 
<john.lil...@redpointglobal.com.invalid<mailto:john.lil...@redpointglobal.com.invalid>>
 wrote:
Greetings,

In our migration from AMQ classic to Artemis, I believe that I’ve found a 
problem.  This is all using JMS and Artemis 2.24.  It would seem that the 
following can happen:

  *   The configuration allows auto-delete.
  *   A queue is in use.  Messages are sent and received.
  *   The consumers of the queue all go away, but producers remain
  *   The queue is auto-deleted
  *   A producer puts a message on the queue.  This seems to fail silently – 
the JMS call succeeds but the queue is not recreated.
  *   Subsequently, this is also revealed by Jolokia calls to enumerate the 
queue length also reporting that either the queue does not exist or it is empty 
(I don’t know which, yet)

This worked just fine with AMQ classic.  So my first question is, is this a 
known issue?  If not, I can cook up an example.

Thanks
John



[rg]<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.redpointglobal.com%2f&c=E,1,dOMufZKXyOLDkhzwrqdbtEBXAmr0osUbT6gKR3Rhg_lif7EIgBnuNNoqr3pX_Fq4Gg9KqARfP8DGXjdA_6jji2ebnqb5CMUUW6Vt2rSpToEDE47bY2NvRRvW&typo=1>

John Lilley

Data Management Chief Architect, Redpoint Global Inc.

888 Worcester Street, Suite 200 Wellesley, MA 02482

M: +1 7209385761<tel:+1%207209385761> | 
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>

PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential 
and is intended solely for the use of the individual(s) to whom it is 
addressed. If you believe you received this e-mail in error, please notify the 
sender immediately, delete the e-mail from your computer and do not copy, print 
or disclose it to anyone else. If you properly received this e-mail as a 
customer, partner or vendor of Redpoint, you should maintain its contents in 
confidence subject to the terms and conditions of your agreement(s) with 
Redpoint.

PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential 
and is intended solely for the use of the individual(s) to whom it is 
addressed. If you believe you received this e-mail in error, please notify the 
sender immediately, delete the e-mail from your computer and do not copy, print 
or disclose it to anyone else. If you properly received this e-mail as a 
customer, partner or vendor of Redpoint, you should maintain its contents in 
confidence subject to the terms and conditions of your agreement(s) with 
Redpoint.

PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential 
and is intended solely for the use of the individual(s) to whom it is 
addressed. If you believe you received this e-mail in error, please notify the 
sender immediately, delete the e-mail from your computer and do not copy, print 
or disclose it to anyone else. If you properly received this e-mail as a 
customer, partner or vendor of Redpoint, you should maintain its contents in 
confidence subject to the terms and conditions of your agreement(s) with 
Redpoint.

Reply via email to