Re: Understanding queue limits

On Fri, Nov 22, 2013 at 8:40 PM, Gordon Sim wrote: > On 11/22/2013 04:29 AM, Paul Colby wrote: > >> Hi, >> >> I'm trying to understand some of the finer details of the queue size >> limits >> / policies, specifically in the context of a 0.16 cluster (I

Understanding queue limits

to? Since I'm making all messages durable, they are all already on disk so flow-to-disk is kind of redundant for me (assuming this is the same store that flow-to-disk refers to?). So I think the policy here should be reject instead (the ring* policies are certainly not what I want). Is my thinking correct? Thanks :) Paul Colby. http://colby.id.au

Re: ACL not working properly?

Hi Parkirat, I'm not sure if this is your issue, but when specifying the broker for qpid-config 0.16, I use the "-b" flag, not "-a". eg: qpid-config -b amqps://parkirat/parkirat@localhost Of course, that flag may have changed for the version your running, and you might want to drop the "amps" bi

Re: ACL to allow QMF agents / clients

to-date. > > -Ted > > > On 05/30/2012 12:09 AM, Paul Colby wrote: > >> Hi, >> >> I'm implementing an access control list (ACL) for an internal Qpid >> cluster. >> Most of the ACL is nice and straight-forward. However, I'm wondering >> w

ACL to allow QMF agents / clients

Hi, I'm implementing an access control list (ACL) for an internal Qpid cluster. Most of the ACL is nice and straight-forward. However, I'm wondering what the best way is to enabled QMF agents and clients to work (we have our own custom QMF agents and clients using QMF2, plus of the standard Qpid

How to set ssl_keyfile / ssl_certfile for python tools from the command line?

Hi guys, It's great to see python SSL support has been (mostly?) fixed up in 0.16! :) Now, I've got qpid-config successfully using SSL to talk to my brokers like: qpid-config -b amqps://localhost However, if I set ssl-require-client-authentication on the brokers, to enable the EXTERNAL mechanis

RPM spec file for 0.16?

Hi, Is there an RPM spec file for 0.16 somewhere? Or should I just extract the 0.14 one from rawhide ( http://mirror.optus.net/fedora/linux/development/rawhide/source/SRPMS/q/qpid-cpp-0.14-3.fc18.1.src.rpm) and modify it accordingly? Thanks :) pc http://colby.id.au

Re: 0.14 cluster never survives more than an hour or so.

run for at least 2 hours without the error. But again, some > QMF based services rely on the updates. > > > Kind regards, > Pavel Moravec > > > - Original Message - > > From: "Paul Colby" > > To: users@qpid.apache.org > > Sent: Friday, April

Re: 0.14 cluster never survives more than an hour or so.

at a time. When more elder nodes >> are present, all invokes the task on every cluster member, causing more >> tasks to be executed - that is prevented by broker shutdown.) >> >> Kind regards, >> Pavel Moravec >> >> >> - Original Message - >> &g

Re: Does the qpid-cluster command support SSL?

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" >

Re: 0.14 cluster never survives more than an hour or so.

shutdown.) > > Kind regards, > Pavel Moravec > > > - Original Message - > > From: "Paul Colby" > > To: users@qpid.apache.org > > Sent: Thursday, April 12, 2012 5:08:01 AM > > Subject: 0.14 cluster never survives more than an hour or so. &

0.14 cluster never survives more than an hour or so.

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 minutes to an hour) all brokers in the cluste

Does the qpid-cluster command support SSL?

Hi, Just wondering, is the qpid-cluster command line utility meant to support SSL somehow? ie If my brokers are configured to require encryption, can I still use the qpid-cluster command? Interested in the answer for both 0.14 (I'm using now), and 0.16 (would love to use soon :) It looks to me

Re: Something change for client SSL support in 0.14?

Found the bug. Creating JIRA... pc http://colby.id.au On Thu, Feb 9, 2012 at 2:51 PM, Paul Colby wrote: > Hi guys, > > Did something change with the way we enable SSL for clients in 0.14? > > I'm trying 0.14 cpp clients to talk to 0.14 cpp brokers. > > My cur

Re: Something change for client SSL support in 0.14?

redacted :5671... Created IO thread: 0 SslConnector created for \x00- Any advice would be much appreciated :) pc http://colby.id.au On Sat, Feb 11, 2012 at 1:08 AM, Gordon Sim wrote: > On 02/09/2012 03:51 AM, Paul Colby wrote: > >> Hi guys, >> >> Did something

Something change for client SSL support in 0.14?

Hi guys, Did something change with the way we enable SSL for clients in 0.14? I'm trying 0.14 cpp clients to talk to 0.14 cpp brokers. My current setup works correctly (ie uses SSL) with 0.12 client / servers, but not 0.14. I'm setting the client-side transport option to SSL. The, if I intenti

Re: qmf-tool error - "Failed: TypeError - __init__() takes at most 2 arguments (3 given)"

n.org/issue1686487). I know Py 2.4 is really old, but I'll put together a jira issue with patch to support Py 2.4 anyway, just in case someone else is stuck on FC / RHEL 5.5 ;) pc http://colby.id.au On Mon, Feb 6, 2012 at 9:28 AM, Paul Colby wrote: > Hi all, > > I'm playing

qmf-tool error - "Failed: TypeError - __init__() takes at most 2 arguments (3 given)"

Hi all, I'm playing with Qpid 0.14 on FC5.5, and everything seems to be working correctly, except for qmf-tool. First, cqpid.py made use of a ternary expression that doesn't seem to be supported by Python 2.4.3 - that was easy to fix. But now I'm just getting this error: Failed: TypeError - __i

Re: qpid-tool bypasses authentication? (Qpid 0.12)

wrote: > On 01/24/2012 11:32 PM, Paul Colby wrote: > >> Hi, >> >> I've just discovered that qpid-stat is NOT affected by qpidd's --auth >> flag. >> Is this expected behaviour? >> >> Specifically, if I run: >> >> qpidd --auth=y

qpid-tool bypasses authentication? (Qpid 0.12)

Hi, I've just discovered that qpid-stat is NOT affected by qpidd's --auth flag. Is this expected behaviour? Specifically, if I run: qpidd --auth=yes Then, my own clients (using the C++ qpid client libraries) fail to connect unless I set username/password, but the following qpid-stat command wo

Re: How to clear the Journal so I can restart C++ Broker?

I'm not exactly sure what the problem is, but you can clear the C++ broker's persistent store via the --truncate=yes option... maybe that's what you're looking for? AFAIK, the only way to grow the store is to recreate the relevant queues... but I'm definitely no expert. Good luck. pc http:/

Re: broker clustering with SSL?

AM, Paul Colby wrote: > >> I have a cluster of two Qpidd brokers - both C++ v0.12 (on CentOS 5.5). >> >> Both brokers have been clustering very happily so far :) >> >> Now, I've enabled both SASL and SSL on both brokers. >> >> I have several client

Re: broker clustering with SSL?

Thanks Gordon, those options look exactly like what I need to dig into :) I'll have a play and report back my results :) Thanks again, pc http://colby.id.au On Fri, Nov 18, 2011 at 3:51 AM, Gordon Sim wrote: > On 11/17/2011 03:08 AM, Paul Colby wrote: > >> I have a clu

Re: broker clustering with SSL?

Hi Hamid, Sorry, I've only used Qpid+SSL on Linux so far - there the SSL cert details are specified via environment variables, but not on Windows. Have a read of this thread - http://apache-qpid-users.2158936.n2.nabble.com/SSL-and-C-client-anyone-have-a-complete-example-td4030718.html (search the

broker clustering with SSL?

Hi, I have a cluster of two Qpidd brokers - both C++ v0.12 (on CentOS 5.5). Both brokers have been clustering very happily so far :) Now, I've enabled both SASL and SSL on both brokers. I have several client applications I've written that can authenticate, and use SSL to talk successfully to ei

Re: can the C++ broker expire really idle connections?

On Mon, Aug 22, 2011 at 6:58 PM, Gordon Sim wrote: > On 08/22/2011 03:08 AM, Paul Colby wrote: > >> Hi, >> >> I have a C++ broker (0.10) running, which has messages stuck in a handful >> of >> queues. It seems that these messages are "stuck" bec

can the C++ broker expire really idle connections?

Hi, I have a C++ broker (0.10) running, which has messages stuck in a handful of queues. It seems that these messages are "stuck" because the broker has given them to one of my consumer processes, which has not yet ack'd/rejected/released the messages. The problem is, the consumer in question di

Re: Durable queues not surviving broker re-start

On 14/04/2011 7:23 PM, Gordon Sim wrote: On 04/14/2011 12:46 AM, Paul Colby wrote: Hi guys, I'm probably missing something here, and/or not understanding what "durable" queues are. If I do the following: 1. start a C++ broker via: qpidd --auth no You need a store plugin loade

Re: Durable queues not surviving broker re-start

Oops... wherever I've written "qpid-tool" below, I meant "qpid-config" ;) eg: qpid-config add queue TEST --durable Paul Colby C++ Developer www.MessageMedia.com.au On 14/04/2011 9:46 AM, Paul Colby wrote: Hi guys, I'm probably missing something here, and/or n

Durable queues not surviving broker re-start

Hi guys, I'm probably missing something here, and/or not understanding what "durable" queues are. If I do the following: 1. start a C++ broker via: qpidd --auth no 2. create a durable queue via: qpid-tool add queue TEST --durable 3. list queues via: qpid-tool queues 4. restart the C++ broker

Message timestamp via Qpid Messaging API?

very message I send, and will do so if that's the only option, but it would be nice to be able to access the broker's built-in timestamp (assuming there is one). Thanks :) Paul Colby. C++ Developer www.MessageMedia.com.au