8:22 PM
> To: users@activemq.apache.org
> Subject: Re: limiting queue creation in JMS durable subscription flow
>
> > ...I’m not 100% sure if this requirement comes from Qpid library which
> > we
> are using, or Camel, or is it a requirement for JMS subscribers in
>
day, April 16, 2025 8:22 PM
> To: users@activemq.apache.org
> Subject: Re: limiting queue creation in JMS durable subscription flow
>
> > ...I’m not 100% sure if this requirement comes from Qpid library which
> > we
> are using, or Camel, or is it a requirement for JMS subs
-
From: Justin Bertram
Sent: Friday, April 18, 2025 5:20 PM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
There are different ways to lock down the broker.
1) You can make it so that external clients can only create exactly the
subscrip
> From: Justin Bertram
> Sent: Thursday, April 17, 2025 5:44 PM
> To: users@activemq.apache.org
> Subject: Re: limiting queue creation in JMS durable subscription flow
>
> The createDurableQueue permission is required for JMS durable subscribers
> (i.e. consumers) since the d
Sent: Thursday, April 17, 2025 5:44 PM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
The createDurableQueue permission is required for JMS durable subscribers (i.e.
consumers) since the durable subscription they create is represented by a
Vilius
>
> -Original Message-
> From: Alexander Milovidov
> Sent: Thursday, April 17, 2025 11:18 AM
> To: users@activemq.apache.org
> Subject: Re: limiting queue creation in JMS durable subscription flow
>
> Permissions can be set for address matches which can be exact
consumer side at all.
--
Vilius
-Original Message-
From: Alexander Milovidov
Sent: Thursday, April 17, 2025 11:18 AM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
Permissions can be set for address matches which can be exact ad
ssage-
From: Alexander Milovidov
Sent: Thursday, April 17, 2025 11:18 AM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
Permissions can be set for address matches which can be exact address name, or
address wildcard, or exact address::queue
ursday, April 17, 2025 10:22 AM
> To: users@activemq.apache.org
> Subject: Re: limiting queue creation in JMS durable subscription flow
>
> Hi Vilius,
>
> If the name of the subscription queue is known, you can create security
> setting for FQQN queue name, for example
> "
ilius
-Original Message-
From: Alexander Milovidov
Sent: Thursday, April 17, 2025 10:22 AM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
Hi Vilius,
If the name of the subscription queue is known, you can create security setting
for FQQN
, April 16, 2025 8:22 PM
To: users@activemq.apache.org
Subject: Re: limiting queue creation in JMS durable subscription flow
> ...I’m not 100% sure if this requirement comes from Qpid library which
> we
are using, or Camel, or is it a requirement for JMS subscribers in general...
Thi
> ...I’m not 100% sure if this requirement comes from Qpid library which we
are using, or Camel, or is it a requirement for JMS subscribers in
general...
This is a requirement for JMS topic subscriptions in general. See the
documentation [1] for more details.
> Is there a way to limit amount of q
12 matches
Mail list logo
