You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Stephen Baker <st...@motorolasolutions.com.INVALID> on 2023/11/06 16:55:10 UTC
Convert queue to configuration managed
Hello,
A problem I've hit a couple times is that we've forgotten to deploy
our updated addresses before deploying the applications that use them.
This ends up succeeding because auto-create is enabled, but the
addresses and queues are configured with auto-delete: true and
configuration-managed: false.
Afterwards when the addresses are properly configured, the properties
on the queue don't change, and auto-delete still happens. So far the
only way I've found is to stop the world so that the queue is not in
use, delete it, and then touch the broker.xml (or abandon the queue
and use a new name)
Is there another way to change the properties on an existing
address/queue so that it can become configuration managed (or at least
not auto-delete).
Other things I tried:
updateQueue() JMX operation (with the name of the queue and
"auto-delete": false.
Stephen E. Baker
--
*For more information on how and why we collect your personal
information, please visit our Privacy Policy
<https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Re: Convert queue to configuration managed
Posted by Domenico Francesco Bruscino <br...@gmail.com>.
Hi Stephen,
there is no way to change the property auto-delete for a running queue but
that could be an improvement for the updateQueue() JMX operation, could you
create a new JIRA issue?
https://issues.apache.org/jira/projects/ARTEMIS/issues
Regards,
Domenico
On Fri, 10 Nov 2023 at 04:42, Stephen Baker
<st...@motorolasolutions.com.invalid> wrote:
> Oh, that's a step!
>
> Do you know if it's possible to get from there to auto-delete: false
> (or I should just try it out)
>
> On Wed, Nov 8, 2023 at 5:28 AM Domenico Francesco Bruscino
> <br...@gmail.com> wrote:
> >
> > Hi Stephen,
> >
> > updateQueue() JMX operation doesn't allow to change the `auto-delete`
> > setting but it allows to change the `configuration-managed` setting, i.e.
> >
> > {"name":"MYQUEUE","configuration-managed":true}
> >
> > Regards,
> > Domenico
> >
> > On Mon, 6 Nov 2023 at 17:55, Stephen Baker
> > <st...@motorolasolutions.com.invalid> wrote:
> >
> > > Hello,
> > >
> > > A problem I've hit a couple times is that we've forgotten to deploy
> > > our updated addresses before deploying the applications that use them.
> > >
> > > This ends up succeeding because auto-create is enabled, but the
> > > addresses and queues are configured with auto-delete: true and
> > > configuration-managed: false.
> > >
> > > Afterwards when the addresses are properly configured, the properties
> > > on the queue don't change, and auto-delete still happens. So far the
> > > only way I've found is to stop the world so that the queue is not in
> > > use, delete it, and then touch the broker.xml (or abandon the queue
> > > and use a new name)
> > >
> > > Is there another way to change the properties on an existing
> > > address/queue so that it can become configuration managed (or at least
> > > not auto-delete).
> > >
> > > Other things I tried:
> > > updateQueue() JMX operation (with the name of the queue and
> > > "auto-delete": false.
> > >
> > > Stephen E. Baker
> > >
> > > --
> > >
> > >
> > > *For more information on how and why we collect your personal
> > > information, please visit our Privacy Policy
> > > <
> > >
> https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement
> > > >.*
> > >
>
> --
>
>
> *For more information on how and why we collect your personal
> information, please visit our Privacy Policy
> <
> https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement
> >.*
>
Re: Convert queue to configuration managed
Posted by Stephen Baker <st...@motorolasolutions.com.INVALID>.
Oh, that's a step!
Do you know if it's possible to get from there to auto-delete: false
(or I should just try it out)
On Wed, Nov 8, 2023 at 5:28 AM Domenico Francesco Bruscino
<br...@gmail.com> wrote:
>
> Hi Stephen,
>
> updateQueue() JMX operation doesn't allow to change the `auto-delete`
> setting but it allows to change the `configuration-managed` setting, i.e.
>
> {"name":"MYQUEUE","configuration-managed":true}
>
> Regards,
> Domenico
>
> On Mon, 6 Nov 2023 at 17:55, Stephen Baker
> <st...@motorolasolutions.com.invalid> wrote:
>
> > Hello,
> >
> > A problem I've hit a couple times is that we've forgotten to deploy
> > our updated addresses before deploying the applications that use them.
> >
> > This ends up succeeding because auto-create is enabled, but the
> > addresses and queues are configured with auto-delete: true and
> > configuration-managed: false.
> >
> > Afterwards when the addresses are properly configured, the properties
> > on the queue don't change, and auto-delete still happens. So far the
> > only way I've found is to stop the world so that the queue is not in
> > use, delete it, and then touch the broker.xml (or abandon the queue
> > and use a new name)
> >
> > Is there another way to change the properties on an existing
> > address/queue so that it can become configuration managed (or at least
> > not auto-delete).
> >
> > Other things I tried:
> > updateQueue() JMX operation (with the name of the queue and
> > "auto-delete": false.
> >
> > Stephen E. Baker
> >
> > --
> >
> >
> > *For more information on how and why we collect your personal
> > information, please visit our Privacy Policy
> > <
> > https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement
> > >.*
> >
--
*For more information on how and why we collect your personal
information, please visit our Privacy Policy
<https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
Re: Convert queue to configuration managed
Posted by Domenico Francesco Bruscino <br...@gmail.com>.
Hi Stephen,
updateQueue() JMX operation doesn't allow to change the `auto-delete`
setting but it allows to change the `configuration-managed` setting, i.e.
{"name":"MYQUEUE","configuration-managed":true}
Regards,
Domenico
On Mon, 6 Nov 2023 at 17:55, Stephen Baker
<st...@motorolasolutions.com.invalid> wrote:
> Hello,
>
> A problem I've hit a couple times is that we've forgotten to deploy
> our updated addresses before deploying the applications that use them.
>
> This ends up succeeding because auto-create is enabled, but the
> addresses and queues are configured with auto-delete: true and
> configuration-managed: false.
>
> Afterwards when the addresses are properly configured, the properties
> on the queue don't change, and auto-delete still happens. So far the
> only way I've found is to stop the world so that the queue is not in
> use, delete it, and then touch the broker.xml (or abandon the queue
> and use a new name)
>
> Is there another way to change the properties on an existing
> address/queue so that it can become configuration managed (or at least
> not auto-delete).
>
> Other things I tried:
> updateQueue() JMX operation (with the name of the queue and
> "auto-delete": false.
>
> Stephen E. Baker
>
> --
>
>
> *For more information on how and why we collect your personal
> information, please visit our Privacy Policy
> <
> https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement
> >.*
>