If the alerts are all you need, maybe as an alternative you can write your own QMF client which would collect the queue statistics and evaluate the alerts on its own.
Jakub On Fri, Oct 9, 2015 at 9:19 PM, Jerome O'Neil <[email protected]> wrote: > Yes I do. C++ brokers. > > I'm not sure recreating the queue is going to be an option for me, as the > client that I want to use to manipulate the configuration isn't the client > that was used to create the queue. > > So I'd have queue X declared and subscribed to by client A. Client B > comes in and deletes it, then recreates it with the necessary > configuration. That seems... unlikely. :) > > What is the process for getting a feature request into the Apache > project? I'd really like to be able to manipulate queue configurations on > a declared queue outside of the declaration. I think that would be useful. > > Best, > > -J > > -----Original Message----- > From: Pavel Moravec [mailto:[email protected]] > Sent: Friday, October 09, 2015 5:37 AM > To: [email protected] > Subject: Re: Modification of queue arguments after declaration > > Hello, > I guess you need that for C++ broker. > > There is no way of reconfiguring a queue like that, you would have to > delete the queue and re-create again with the extra parameters added. > > > Kind regards, > Pavel > > > ----- Original Message ----- > > From: "Jerome O'Neil" <[email protected]> > > To: [email protected] > > Sent: Thursday, 8 October, 2015 8:57:39 PM > > Subject: Modification of queue arguments after declaration > > > > I need to be able to modify the configuration of specific queues after > > they have been declared. The schema tells me that the arguments > > element is a ReadOnly property. > > > > Specifically, I'd like to be able to add "qpid.alert_count" and > > "qpid.alert_repeat_gap" to specific queues. I can access the new > > queues as QMF sends me events when they are declared, but I'm unsure > > how I can modify these two arguments. > > Is there some other way to achieve this? > > > > Best, > > > > -Jerome > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
