On Wed, 2014-09-24 at 10:40 -0700, Spencer.Doak wrote:
> Hi,
>
> Well as you know, I'm definitely in support of this addition.
>
> I do not know how the exact details about the QMF listener, but I would
> imagine it could receive the shutdown message and do something like
> "std::exit(1);". Of co
On Wed, 2014-09-24 at 20:29 +0200, Jakub Scholz wrote:
> What do you expect the shutdown call to do in clustered brokers? Shutdown
> the whole cluster or just the active node?
Just the active node. I would think of it as being equivalent to a
remote kill -TERM. Useful if you don't have ssh or othe
>
> - Original Message -
> > From: "Alan Conway"
> > To: users@qpid.apache.org
> > Cc: "Chuck Rolke" , "Gordon Sim"
> > Sent: Monday, September 22, 2014 4:10:12 PM
> > Subject: Add qmf shutdown command to the broker [was Re: QPID C+
What do you expect the shutdown call to do in clustered brokers? Shutdown
the whole cluster or just the active node?
Personally, I don't really see the value in it. But at the same time - if
it is properly secured with ACLs - I don't think its a big security issue.
Regards
Jakub
On Mon, Sep 22,
huck Rolke" , "Gordon Sim"
> Sent: Monday, September 22, 2014 4:10:12 PM
> Subject: Add qmf shutdown command to the broker [was Re: QPID C++ -
> Dynamically Managing Broker]
>
> On Thu, 2014-09-18 at 15:12 -0700, Spencer.Doak wrote:
> > Hey Gordon,
> &
alling the exit command; however, I would guess that it's probably a pretty
easy command to implement.
Best Regards,
Spencer
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPID-C-Dynamically-Managing-Broker-tp7613792p7614174.html
Sent from the Apache Qpid users mai
Kind regards,
Pavel
- Original Message -
> From: "Alan Conway"
> To: users@qpid.apache.org
> Cc: "Chuck Rolke" , "Gordon Sim"
> Sent: Monday, September 22, 2014 10:10:12 PM
> Subject: Add qmf shutdown command to the broker [was Re: QPID
On Thu, 2014-09-18 at 15:12 -0700, Spencer.Doak wrote:
> Hey Gordon,
>
> Thank you very much! That should give me a great start on this task.
>
> As for the 'shutdown' command, that's actually exactly what I was thinking
> too. I'm thinking about running a receiver process on the broker machine.
en reading through the
source.
For reference, I'm running the the QPID C++ Broker with QPID C++ Messaging
API 0.28. If I run into any issues with it malfunctioning, I'll post a reply
here.
Thank you,
Spencer
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPID-C-
On 09/19/2014 06:21 PM, Spencer.Doak wrote:
Sorry to be a bother, but I'm having two problems using the code you
attached. The code is great, but when I go to create a queue, the queue is
improperly named. Rather than using the name which is supplied, the queue
created seems to be named using a U
p://qpid.2158936.n2.nabble.com/file/n7613914/qmf_create_queue.py>
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPID-C-Dynamically-Managing-Broker-tp7613792p7613914.html
Sent from the Apache Qpid users mailing list archive at
dvance,
Spencer
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPID-C-Dynamically-Managing-Broker-tp7613792p7613863.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscr
On 09/18/2014 12:56 AM, Spencer.Doak wrote:
Hello,
I'm faced with a bit of an issue. For an application I'm working on, I'm in
need of several abilities:
1. Create, destroy, and clear queues on an exchange.
2. Create and destroy exchanges on a broker.
3. Fetch a list of all existing connections
ew this message in context:
http://qpid.2158936.n2.nabble.com/QPID-C-Dynamically-Managing-Broker-tp7613792.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.ap
14 matches
Mail list logo
