Re: Temporary queue in Artemis active MQ
I guess you are asking for updates because you are not receiving the replies to users@activemq.apache.org. I suppose it is happening because you didn't subscribe users@activemq.apache.org. See the replies of Erwin, Justin and Alexander at https://lists.apache.org/thread/9h2sdp7y5kg05p8qy77d5clnn8v1jkk2 On Thu, 25 Apr 2024 at 08:40, Alexander Milovidov wrote: > Hi Naveen, > > I'm not an expert in ActiveMQ Artemis, and may answer incorrectly, but I > have seen some cases when temporary queues are used. > Usually there is no need to use management API to create a temporary queue. > As it seems to me, the purpose of temporary queues is to be auto-created > and auto-deleted without any management actions. > > Temporary queue is created under some address, and the address can also be > temporary (if the application has permissions to delete it when > disconnecting). > For example, when running JMSToolBox (open source utility for working with > different message brokers), it connects to Artemis and creates (or requests > to auto-create?) an address with an UUID-like name with the same queue. > > Another case of using temporary queues is non-durable subscription. When an > application subscribes to the topic (multicast address), in some conditions > it creates a temporary queue on this address. > There should be createNonDurableQueue, deleteNonDurableQueue permissions on > this address, and createAddress if an address also doesn't exist. As far as > I know, address-settings should also allow auto-creation of addresses and > queues. > > Permissions can be granted to the address and fully-qualified queue name, > but temporary queue names are usually random. If an application uses a > temporary queue on the specific address, it is possible to grant > permissions to this address (and all queues on this address). > It is not possible to specify granular permissions for the address when > it's name is random, but one of our developers has made some small change > in JMSToolBox Artemis module which adds some prefix to the name, so we can > add permissions on this prefix and grant any user to connect with > JMSToolBox without having full permissions on the broker. > We have used two methods to configure permissions: API operation > addSecuritySettings, and security-settings in the broker.xml (the latter > was preferable for us). > > ср, 24 апр. 2024 г. в 19:30, Naveen kumar : > > > Hi Team, > > > > Any update please ? > > > > Regards , > > Naveen > > > > On Mon, 22 Apr 2024 at 16:35, Justin Bertram wrote: > Erwin responded [1] almost a week ago now. Did you have additional > questions? > > > Justin > > [1] https://lists.apache.org/thread/9h2sdp7y5kg05p8qy77d5clnn8v1jkk2 > > > On 22 Apr 2024, at 5:25 PM, Naveen kumar > wrote: > > > > > > Hi Team, > > > > > > Any update on below please ? > > > > > > Regards, > > > Naveen > > > > > On Tue, 16 Apr 2024 at 19:07, Dondorp, Erwin > wrote: > > Hi Team, > Actually, this is a community > > > 1. When are temporary queues used ? > Most common is for request-reply patterns. > Where the reply-message is returned on a temporary queue, for which the > queue-name is passwd in the request message (field reply-to). > Since the reply-queue typically has a long/generated name (e.g. based on a > uuid) only the original request-sender can get the reply. > It's just that no-one else knows that name. > > > 2. How are temporary queues created ? > e.g. in JMS with function createTemporaryQueue(...) > > > 3. Is there any API call to create temporary queue using JMX? > Did not find one (and did not expect one). > It is up to the client software to create the temporary queue, see (1) > > 4. How can granular access management for temporary queues are specified > From an address point of view, it behaves the same as a regular > address/queue. > So you should be able to assign access-properties to it. > But since in a typical case, the name is based on a uuid it is hard to > assign specific permissions to individual temporary queues. > But the good thing is that other subscribers don't know the name of your > temporary queues due to the uuid in the names. > > Erwin > > >> On 16 Apr 2024, at 11:59 AM, Naveen kumar > > wrote: > > >> > > >> Hi Team, > > >> > > >> We have the below question on temporary queues in Artemis MQ in eks . > > Could you please help us with answer for the below ones, > > >> > > >> 1. When are temporary queues used ? > > >> 2. How are temporary queues created ? > > >> 3. Is there any API call to create temporary queue using JMX? > > >> 4. How can granular access management for temporary queues are > specified > > >> > > >> > > >> Regards, > > >> Naveen > > >
Re: Temporary queue in Artemis active MQ
Hi Naveen, I'm not an expert in ActiveMQ Artemis, and may answer incorrectly, but I have seen some cases when temporary queues are used. Usually there is no need to use management API to create a temporary queue. As it seems to me, the purpose of temporary queues is to be auto-created and auto-deleted without any management actions. Temporary queue is created under some address, and the address can also be temporary (if the application has permissions to delete it when disconnecting). For example, when running JMSToolBox (open source utility for working with different message brokers), it connects to Artemis and creates (or requests to auto-create?) an address with an UUID-like name with the same queue. Another case of using temporary queues is non-durable subscription. When an application subscribes to the topic (multicast address), in some conditions it creates a temporary queue on this address. There should be createNonDurableQueue, deleteNonDurableQueue permissions on this address, and createAddress if an address also doesn't exist. As far as I know, address-settings should also allow auto-creation of addresses and queues. Permissions can be granted to the address and fully-qualified queue name, but temporary queue names are usually random. If an application uses a temporary queue on the specific address, it is possible to grant permissions to this address (and all queues on this address). It is not possible to specify granular permissions for the address when it's name is random, but one of our developers has made some small change in JMSToolBox Artemis module which adds some prefix to the name, so we can add permissions on this prefix and grant any user to connect with JMSToolBox without having full permissions on the broker. We have used two methods to configure permissions: API operation addSecuritySettings, and security-settings in the broker.xml (the latter was preferable for us). ср, 24 апр. 2024 г. в 19:30, Naveen kumar : > Hi Team, > > Any update please ? > > Regards , > Naveen > > > On 22 Apr 2024, at 5:25 PM, Naveen kumar wrote: > > > > Hi Team, > > > > Any update on below please ? > > > > Regards, > > Naveen > > > >> On 16 Apr 2024, at 11:59 AM, Naveen kumar > wrote: > >> > >> Hi Team, > >> > >> We have the below question on temporary queues in Artemis MQ in eks . > Could you please help us with answer for the below ones, > >> > >> 1. When are temporary queues used ? > >> 2. How are temporary queues created ? > >> 3. Is there any API call to create temporary queue using JMX? > >> 4. How can granular access management for temporary queues are specified > >> > >> > >> Regards, > >> Naveen >
Re: Temporary queue in Artemis active MQ
Hi Team, Any update please ? Regards , Naveen > On 22 Apr 2024, at 5:25 PM, Naveen kumar wrote: > > Hi Team, > > Any update on below please ? > > Regards, > Naveen > >> On 16 Apr 2024, at 11:59 AM, Naveen kumar wrote: >> >> Hi Team, >> >> We have the below question on temporary queues in Artemis MQ in eks . Could >> you please help us with answer for the below ones, >> >> 1. When are temporary queues used ? >> 2. How are temporary queues created ? >> 3. Is there any API call to create temporary queue using JMX? >> 4. How can granular access management for temporary queues are specified >> >> >> Regards, >> Naveen
Re: Temporary queue in Artemis active MQ
Erwin responded [1] almost a week ago now. Did you have additional questions? Justin [1] https://lists.apache.org/thread/9h2sdp7y5kg05p8qy77d5clnn8v1jkk2 On Mon, Apr 22, 2024 at 9:00 AM Naveen kumar wrote: > Hi Team, > > Any update on below please ? > > Regards, > Naveen > > > On 16 Apr 2024, at 11:59 AM, Naveen kumar > wrote: > > > > Hi Team, > > > > We have the below question on temporary queues in Artemis MQ in eks . > Could you please help us with answer for the below ones, > > > > 1. When are temporary queues used ? > > 2. How are temporary queues created ? > > 3. Is there any API call to create temporary queue using JMX? > > 4. How can granular access management for temporary queues are specified > > > > > > Regards, > > Naveen > >
Re: Temporary queue in Artemis active MQ
Hi Team, Any update on below please ? Regards, Naveen > On 16 Apr 2024, at 11:59 AM, Naveen kumar wrote: > > Hi Team, > > We have the below question on temporary queues in Artemis MQ in eks . Could > you please help us with answer for the below ones, > > 1. When are temporary queues used ? > 2. How are temporary queues created ? > 3. Is there any API call to create temporary queue using JMX? > 4. How can granular access management for temporary queues are specified > > > Regards, > Naveen
RE: Temporary queue in Artemis active MQ
> Hi Team, Actually, this is a community > 1. When are temporary queues used ? Most common is for request-reply patterns. Where the reply-message is returned on a temporary queue, for which the queue-name is passwd in the request message (field reply-to). Since the reply-queue typically has a long/generated name (e.g. based on a uuid) only the original request-sender can get the reply. It's just that no-one else knows that name. > 2. How are temporary queues created ? e.g. in JMS with function createTemporaryQueue(...) > 3. Is there any API call to create temporary queue using JMX? Did not find one (and did not expect one). It is up to the client software to create the temporary queue, see (1) 4. How can granular access management for temporary queues are specified From an address point of view, it behaves the same as a regular address/queue. So you should be able to assign access-properties to it. But since in a typical case, the name is based on a uuid it is hard to assign specific permissions to individual temporary queues. But the good thing is that other subscribers don't know the name of your temporary queues due to the uuid in the names. Erwin -Original Message- From: Naveen kumar Sent: Tuesday, April 16, 2024 8:29 AM To: users@activemq.apache.org Subject: Temporary queue in Artemis active MQ EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Team, We have the below question on temporary queues in Artemis MQ in eks . Could you please help us with answer for the below ones, 1. When are temporary queues used ? 2. How are temporary queues created ? 3. Is there any API call to create temporary queue using JMX? 4. How can granular access management for temporary queues are specified Regards, Naveen
