Hi Paul,
I think the answer is no, as all qpid-* tools are Python-based and SSL
support in Python client is not resolved fully - see
https://issues.apache.org/jira/browse/QPID-3175 for details.
Kind regards,
Pavel Moravec
- Original Message -
From: Paul Colby p...@colby.id.au
To:
Hi Paul,
this usually happens as a consequence of cluster split-brain. Are you using
CMAN (Cluster Manager)?
(Technically, when split brain occurs, two (or more) qpid brokers think they
are the elder nodes (elder node = the managing node, usually the node that is
oldest in the cluster). But
On 04/12/2012 04:08 AM, Paul Colby wrote:
Hi guys,
I'm having an issue with my new 0.14 cluster, where the same configuration
was fine with 0.12.
The cluster starts up, and all brokers are happy. Then, with no client
activity at all, after some seemingly random amount time (usually around 30
Hello,
having Java client and C++ broker, I want to implement selective consumption of
messages from a queue (something like JMS message selectors in Java broker).
I.e.:
1) Having CLIENT_ACKNOWLEDGE mode,
2) In a loop through all messages of the queue:
a) receive a message
b) decide if to
On Thu, Apr 12, 2012 at 9:53 AM, Pavel Moravec pmora...@redhat.com wrote:
Hello,
having Java client and C++ broker, I want to implement selective
consumption of messages from a queue (something like JMS message selectors
in Java broker). I.e.:
1) Having CLIENT_ACKNOWLEDGE mode,
2) In a
Thanks Pavel and Gordon, I really appreciate you guys getting back to me so
quickly :)
I'm not currently using cman. I hadn't been using it on 0.12 either. I
suspect that split-brain is not the case, since the test cluster in
question on on virtual machines all within a single host, with *very*
