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
On Wed, 2014-09-24 at 14:00 -0400, Chuck Rolke wrote:
> This makes sense as a useful command:
>
> 1. Must have ACL control.
> 2. Only do the 'most orderly shutdown' as if SIGINT or SIGTERM was received.
> 3. No RestartBroker switch.
>
+1 all of the above.
>
> - Original Message -
> > F
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,
This makes sense as a useful command:
1. Must have ACL control.
2. Only do the 'most orderly shutdown' as if SIGINT or SIGTERM was received.
3. No RestartBroker switch.
- Original Message -
> From: "Alan Conway"
> To: users@qpid.apache.org
> Cc: "Chuck Rolke" , "Gordon Sim"
> Sent: Mon
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 course there might be some necessary clean-up before
calling the exit c
Just for information purposes the next release of ActiveMQ which hopes
to use Proton 0.8 once it's released has now moved onto support for JDK
7 and dropped official support for JDK 6.
On 09/24/2014 10:24 AM, Robbie Gemmell wrote:
The compilation issue I missed in the patch was test-only this
This works :)
Thanks Gordon!
-
Best Regards,
Hamid.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPID-0-28-C-Client-Subscribtion-to-Queues-or-Topics-AMQP-1-0-tp7614162p7614168.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---
On 09/24/2014 03:06 PM, Hamid.Shahid wrote:
Hi,Please let me know, if there is a way to add destination type prefix,
'queue' or 'topic' while subscribing to a Queue or Topic using QPID 0.28
(amqp 1.0) C++ Client.For example, ActiveMQ uses queue:// or topic://
prefixes.
Yes, you just need to quo
The compilation issue I missed in the patch was test-only this time, but it
could have as easily been in non-test code. The other tests now failing
might actually point to some functionality under test not working under
Java 6 at runtime though, which is more of an issue. If the tests showing
it di
Hi,Please let me know, if there is a way to add destination type prefix,
'queue' or 'topic' while subscribing to a Queue or Topic using QPID 0.28
(amqp 1.0) C++ Client.For example, ActiveMQ uses queue:// or topic://
prefixes. Kind Regards,Hamid Shahid
-
Best Regards,
Hamid.
--
View this mess
Hi all,
With Qpid 0.30 we have made the move to requiring Java 7+. Currently,
proton still allows for use of Java 6, so I wonder what peoples thoughts
are on the timing of a similar move for Proton? I'd personally like to do
it soon since Java 6 is EOL, but if not then I think we should at least
d
Hi Andrew,
cool, thanks! I will open a Jira and provide my changes.
I had to copy some stuff (without any changes) from
qpid/posix/SystemInfo.cpp to qpid/solaris/SystemInfo.cpp.
The qpidd ist running now on Solaris and the testprogram "qpid-ping" is
running without any problem. I can also a
12 matches
Mail list logo
