Re: QMF2

Hi Cajus, QMF2 is still under development in 0.6, it's likely to see changes to the api as development continues. thanks, -K - Cajus Pollmeier ca...@naasa.net wrote: Hi, I'd like to make use of QMF2 in a management scenario. After reading the available docs from the wiki, I was

Re: QMF 2 creating child managed objects

Hi, But when I go to run the create_child method it returns: outMap contains status=2 and statusText=UnknownMethod. Why is it an unknown method? The ParentComponent generated code in ParentComponent.cpp should have a method called doMethod(), which handles the method call on the agent. By

Re: QMF2 unbind doesn't seem to work for default direct exchange

Kind of related to this - I've not figured out a way to do --passive when adding a queue or exchange with QMF2 it doesn't seem to be one of the properties on create queue. Any ideas on that one? It appears that the --passive option is only supported by the queue.declare and exchange.declare

Re: QMF2 protocol query only seems to support OBJECT target

Hi, There are a couple of directories related to QMF - here's a quick summary: qpid/cpp/src/qpid/management - this is the implementation of the QMF agent in the QPID broker itself. It is used to manage the broker. This supports QMFv2 format object queries and method calls, but schema data is

Re: qpid-config - what does q._altExchange_.name do??

Oh! I've seen this before! In the pure python implementation of the qmf console (see qpid/extras/qmf/ ... /console.py), there's some syntactic sugar that allows the application to fetch a QMF object when given a attribute of an Object Id is surrounded by _'s! Specifically, for:

Re: qpid-config slow

Alan's correct - I *believe* (not looking at the code in the debugger ATM) that qpid-config is most likely downloading the broker schema data on connection, and perhaps parsing that - all under python. So I don't think bringing up the connection is the problem - it's more like pulling in all

Re: QMF2 _agent_locate_response

Hello, I've successfully sent a QMF2 _agent_locate_request and got a _agent_locate_response back, but I'm now wondering what use it is So is the broker agent the only QMF2 agent running by default? I get qmf.opcode = _agent_locate_response qmf.agent =

Re: qpid-config slow

really want to pinpoint the source of the perf issue first - my theory could be wrong. Carl. On 07/21/2011 01:47 PM, Ken Giusti wrote: Alan's correct - I *believe* (not looking at the code in the debugger ATM) that qpid-config is most likely downloading the broker schema data

Re: qpid 0.12 c++ broker make check queue_flow_limit_tests fails

Hmm... no immediate ideas. It appears that, under some circumstances, these queues are being created without the flow control configuration being applied. I have no idea why - I can try to reproduce on a VM running the same setup. Alex - if you'd like to try to debug this, can you alter the

Re: qpid 0.12 c++ broker make check queue_flow_limit_tests fails

enqueued on test-q But it's too late at this point, the test has timed out. That's my best guess as to what is happening. But I'm at a loss as to why those tests are running so slowly. -K - Original Message - On Sep 7, 2011, at 9:53 AM, Ken Giusti wrote: Alex - if you'd like to try

Re: looking for QMF agent/console sample

Hi Daryoush, There are some basic examples in qpid/cpp/bindings/qmf2/examples/cpp/ directory. See: agent.cpp - an example agent that exposes some method calls (like echo). list_agents.cpp - an example console that listens for agents connecting to a broker. Unfortunately, there are no examples

Re: looking for QMF agent/console sample

Yes - equivalent examples for a python agent and client can be found in cpp/bindings/qmf2/examples/python directory. -K - Original Message - Would it be possible to write an agent in python also? Daryoush On Wed, Nov 9, 2011 at 2:01 PM, Ken Giusti kgiu...@redhat.com wrote

Re: QMF and Broker Management

+1 - totally agree with this proposal. - Original Message - Users and Devs, I'd like to make a proposal and start a discussion about the future of QMF and Qpid broker management. QMF (Qpid Management Framework) started out as a way to remotely manage the Qpid C++ broker using

Re: Writing wrong filter in a QMF method causes the filter is ignored

Pavel - I agree that behavior is unexpected - the command should fail without modifying the queue. Can you raise a JIRA and assign it to me? thanks -K - Original Message - Hi, I realized one particular (for me) unexpected behavior when using filters in QMF methods (in C++ broker).

Re: Straw Poll: proposal to remove certain features from qpidd

I really like the refactor, and would rather see it sooner than later, so I'm good with (a)! -K - Original Message - So, to follow up and summarise this thread so far, the only contentious point has been the loss of the 'flow to disk' functionality. Though the current solution

Re: Tested Linux platforms with 0.18

Hi Sean, Like Darryl, I do most of my qpid work using the latest Fedora. However, I was able to build the latest stable branch of qpid (0.18) successfully on my Centos 6 x86_64 machine (fully up to date). Can you cut and paste your build errors into an email? thanks, -K - Original

Re: Tested Linux platforms with 0.18

-- not without reading the whole configure or make script. Hopefully this sheds more light on my situation. On Fri, Oct 26, 2012 at 1:47 PM, Ken Giusti kgiu...@redhat.com wrote: Hi Sean, Like Darryl, I do most of my qpid work using the latest Fedora. However, I was able to build

Re: QMF dead to new requests after invoking some create calls

Hi Fraser, I expect I'm probably pushing the bounds of QMF with this stuff, though if I do: qpid-config bind amq.match test f1 all k1=v1 qpid-config bind amq.match test f1 any k1=v1 I don't get any errors from qpid-config, but the broker says 2013-01-02 14:49:39 error Detected two management

Re: QMF dead to new requests after invoking some create calls

couple of days, I'm currently going through some final bugs snags and a little bit of work to get it looking nice on mobile browsers. Regards, Frase On 03/01/13 17:32, Ken Giusti wrote: This appears to be a bug in the way the amq.match (Headers Exchange) is implemented. The exchange

Re: mailing lists and fragmented communication

I'm in favor of combining them all into one. If not that, then at least collapse the proton list. The level of traffic on that list isn't unreasonable, and, frankly, keeping it separate probably leads to some of the confusion we're seeing over the goals of this project. -K - Original

Re: mailing lists and fragmented communication

there is actually a lot more work that needs to be done surrounding project structure, identity, documentation, communication, etc, and simply rearranging lists without doing the rest of that work is IMHO jumping the gun. --Rafael On Fri, Jan 18, 2013 at 1:14 PM, Ken Giusti kgiu

Re: Broker Federation - replying to queue

a queue from the other broker in the replyTo field with no exchange defined. Thank you, Regards. On Sex, 2013-02-01 at 10:43 -0500, Ken Giusti wrote: Hi Bruno, Since federation routes are uni-directional, you'd need to create another route to get from b2 back to b1 for the response

Re: Some questions on 0.20 QMF Management Objects

Hi Fraser, There's been a lot of new additions to the Broker object which mostly look useful, but what's the intention of the get/set TimestampConfig? How would timestamping received messages be used? That feature provides for the timestamp as described in AMQP 0.10 message.delivery-properties.

Re: Some questions on 0.20 QMF Management Objects

Hi Fraser, Missed this: I'm curious about the query method on the Broker object, what's the point of this? Debug-ability. Its intent is to provide debug information for a given broker object, not to substitute for the information already available in the schema. The QMF schema for a Queue

Re: Error from qpidd while creating queues

Hmm... that would probably be caused by the new queue's management ID colliding with the old queue's ID. The old queue ID is kept around by the management agent so it can notify that the queue was deleted. There was a bug like this that we fixed awhile back: QPID-3666. With the current code,

Re: Error from qpidd while creating queues

Hi Scree, I doubt that this bug will affect sending or receiving messages to that queue. It may affect the management of the queue - like using qpid-stat or qpid-tool to look at the state of the queue (messages queued, etc). I am using qpid 0-10 c++ apis. The bug is/was in the broker daemon

Re: [c++]: Progressing AMQP 1.0 support for 0.22 release

- Original Message - From: Gordon Sim g...@redhat.com To: users@qpid.apache.org Sent: Monday, March 18, 2013 3:07:30 PM Subject: Re: [c++]: Progressing AMQP 1.0 support for 0.22 release On 03/14/2013 01:08 PM, Gordon Sim wrote: As an additional but separate step I'd like to add

Re: [c++]: Progressing AMQP 1.0 support for 0.22 release

address (? is it -a, or -b?). I'll stop grousing now... :) - Original Message - From: Gordon Sim g...@redhat.com To: users@qpid.apache.org Sent: Tuesday, March 19, 2013 11:19:03 AM Subject: Re: [c++]: Progressing AMQP 1.0 support for 0.22 release On 03/19/2013 12:26 PM, Ken Giusti wrote

Re: [c++]: Progressing AMQP 1.0 support for 0.22 release

- Original Message - From: Gordon Sim g...@redhat.com To: users@qpid.apache.org Sent: Thursday, March 21, 2013 11:47:38 AM Subject: Re: [c++]: Progressing AMQP 1.0 support for 0.22 release On 03/21/2013 01:19 PM, Ken Giusti wrote: H... seems like there's not a strong opinion

Re: Questions from a novice

Hi Bill (and Gordon) - sorry about not chiming in a bit earlier with this. Bill - though you've probably already seen it, the management schema is the definitive source for the format of all management objects made available via QMF: qpid/specs/management-schema.xml. It also defines the keys

Re: Questions from a novice

Hi Bill, I've just tried to restrict my broker to using only qmf v2: $ qpidd --auth no --mgmt-qmf1 no and I no longer get update notifications from my console.py app! From the looks of it, the console.py code is broken - the broker is generating the qmfv2 updates, but console.py is dropping

Re: Questions from a novice

...@gmail.com To: users@qpid.apache.org Sent: Monday, April 1, 2013 5:21:46 PM Subject: Re: Questions from a novice Ken, On Mon, Apr 1, 2013 at 4:31 PM, Ken Giusti kgiu...@redhat.com wrote: 2) uniquely identifying objects across multiple brokers. Yes, Gordon's correct, object names

Re: Questions from a novice

- Original Message - From: Bill Freeman ke1g...@gmail.com To: users@qpid.apache.org Sent: Monday, April 1, 2013 7:50:16 PM Subject: Re: Questions from a novice Ken, On Mon, Apr 1, 2013 at 5:58 PM, Ken Giusti kgiu...@redhat.com wrote: That sounds delux, since they would

Re: Questions from a novice

, at 21:31, Ken Giusti kgiu...@redhat.com wrote: Hi Bill, I've just tried to restrict my broker to using only qmf v2: $ qpidd --auth no --mgmt-qmf1 no and I no longer get update notifications from my console.py app! From the looks of it, the console.py code is broken

Re: Questions from a novice

Apr 2013, at 14:26, Ken Giusti kgiu...@redhat.com wrote: Hi Frase, What I saw surprised me: when I disabled v1 (via --mgmt-qmf1 no) and I ran qpid-tool, qpid-tool didn't get any updates (no objects listed). As you point out, the broker should be sending unsolicited object update

Re: Questions from a novice

- Original Message - From: Bill Freeman ke1g...@gmail.com To: users@qpid.apache.org Sent: Wednesday, April 3, 2013 9:45:49 AM Subject: Re: Questions from a novice On Tue, Apr 2, 2013 at 5:22 PM, Ken Giusti kgiu...@redhat.com wrote: When console.py connects to a broker (via

Re: Questions from a novice

- Original Message - From: Bill Freeman ke1g...@gmail.com To: users@qpid.apache.org Sent: Friday, April 5, 2013 12:45:02 PM Subject: Re: Questions from a novice Ken, Yes, with the patch in, I get callbacks to my qmf.console.Console sub-class instance's callback methods for

Re: Questions from a novice

- Original Message - From: Bill Freeman ke1g...@gmail.com To: users@qpid.apache.org Sent: Friday, April 5, 2013 2:37:23 PM Subject: Re: Questions from a novice On Fri, Apr 5, 2013 at 2:09 PM, Ken Giusti kgiu...@redhat.com wrote: - Original Message - From: Bill

Re: Maybe bug, maybe novice mistake, or maybe my python qpid library is too old.

Good catch Bill - this is a bug, and I've entered a JIRA for it: https://issues.apache.org/jira/browse/QPID-4732 That said, I would urge you not to use the QPID connection directly. The API doesn't explicitly expose this, and we probably will be moving the QMF client to use the client

Re: How to set ssl_keyfile and ssl_certfile for python tools (to c++ broker) from the command line?

Hi D James, I'm pretty sure the ssl options were added to qpid-config _after_ 0.18. I think they first appeared in the 0.20 release. Does qpid-config --help list them? -K - Original Message - From: djames dpgja...@gmail.com To: users@qpid.apache.org Sent: Tuesday, April 9, 2013

Re: Maybe bug, maybe novice mistake, or maybe my python qpid library is too old.

- Original Message - From: Bill Freeman ke1g...@gmail.com To: users users@qpid.apache.org Sent: Wednesday, April 10, 2013 11:23:04 AM Subject: Re: Maybe bug, maybe novice mistake, or maybe my python qpid library is too old. Ken, snip As long as I have your attention, does

Re: Plans for QMF v1 and v2 (was Re: QMFv2 object update bug [WAS Re: Questions from a novice])

6, 2013 7:11:18 AM Subject: Plans for QMF v1 and v2 (was Re: QMFv2 object update bug [WAS Re: Questions from a novice]) On 05/03/2013 04:51 PM, Ken Giusti wrote: I want to know what the QPID project's plan is for QMFv1/v2 support in the C++ broker going forward. If the consensus

QPID code reorg/cleanups - please read.

Folks, There's some old QMF-related code in our repo that appears to be quite dead. If said code is in fact pushing up the daisies, I'd like to see removed prior to the 0.24 release. First, there's stuff that I'm almost certain is stone cold dead. AFAIK, this shouldn't be used by anyone. It

Re: [c++]: autodelete, authorisation and QMF event

+1 to this proposal. Re: queueDelete/exchangeDelete events - my preference would be to add an autoDel flag to the existing events, setting it true in the case of the auto delete, and false if the delete occurred by mgmt request. I suppose, on auto-delete 'rhost' and 'user' would take on the

Re: QPID code reorg/cleanups - please read.

- Original Message - From: Fraser Adams fraser.ad...@blueyonder.co.uk To: d...@qpid.apache.org, users@qpid.apache.org Sent: Wednesday, June 19, 2013 3:04:08 PM Subject: Re: QPID code reorg/cleanups - please read. On 18/06/13 23:30, Ken Giusti wrote: Folks, There's some old

Re: proposed removal of qpid::client API (was Re: QPID code reorg/cleanups - please read.)

Good point Bill - I've created a JIRA to cut the console over to the messaging api: https://issues.apache.org/jira/browse/QPID-4945 Though, technically, I don't think we can easily remove the old client API from the _python_ client. IIRC, the new messaging api depends on it. -

Re: proposed removal of qpid::client API (was Re: QPID code reorg/cleanups - please read.)

python QMF console.py uses the old client api from the original python native client. No deps on any C++ stuff. - Original Message - From: Andrew Stitcher astitc...@redhat.com To: users@qpid.apache.org Sent: Friday, June 21, 2013 3:40:11 PM Subject: Re: proposed removal of

Re: C++ Broker QMF Exchange byte statistics don't seem to be being updated

Hi Fraser, You're not imagining it - I've got the same results, those counters never increment (stay at zero). Seems like a problem with the C++ broker's message content accounting. I've popped open a JIRA: https://issues.apache.org/jira/browse/QPID-4950 I'll need to fix this for 0.22

Please read: Change to C++ broker default behavior wrt QMF

Folks, I've made a change on trunk to the way the C++ Broker generates unsolicited management update messages (i.e. object update notification messages and event messages). [1] Previous to this change, the broker would transmit two messages for each management event and object update - one in

Re: Telling v1 events from v2 events using qmf.console python QMF library

can make my patch the same way, knowing that when I get around to accepting a new enough released version to obviate the need for my patched one, my code won't have to change in this area. Bill On Thu, Jul 25, 2013 at 3:58 PM, Ken Giusti kgiu...@redhat.com wrote: Hi Bill, I don't

Re: Telling v1 events from v2 events using qmf.console python QMF library

events from v2 events using qmf.console python QMF library Ken, It works for me. Bill On Thu, Jul 25, 2013 at 6:43 PM, Ken Giusti kgiu...@redhat.com wrote: Hi Bill, Care to try out a patch for me? https://issues.apache.org/jira/browse/QPID-5019 If this works, I'll try

Is anyone using the QMF C++ Agent and Console development libraries (libqmf2)?

Hi All, Before I start investing time working on https://issues.apache.org/jira/browse/QPID-5226 and https://issues.apache.org/jira/browse/QPID-4981, I was wondering if anyone actually uses these C++ libraries. As far as I can tell, the code hasn't seen any serious development in over two

Re: using proton messenger *asynchronously*

) Justin - can you remove those old proton api docs Fraser hit from our web site? http://qpid.apache.org/components/messenger/book/sending-and-receiving.html thanks, -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: users@qpid.apache.org Sent: Tuesday, November 19, 2013 3

Python wrapper - SASL and SSL class API

Hi all - just wanted to get some opinions on $Subject: While I was trying to implement a fix for https://issues.apache.org/jira/browse/PROTON-476 I found that the lifecycle model for the python SASL and SSL objects differs for the C engine. I think the python wrapper's impl is buggy. In

Re: Python wrapper - SASL and SSL class API

- Original Message - From: Rafael Schloming r...@alum.mit.edu To: pro...@qpid.apache.org Cc: users@qpid.apache.org Sent: Wednesday, December 11, 2013 9:43:59 AM Subject: Re: Python wrapper - SASL and SSL class API On Wed, Dec 11, 2013 at 9:35 AM, Ken Giusti kgiu...@redhat.com

Re: 0.26 release update - RC2 is available

+1 Tested by installing on a bare-bones Centos 5.10 VM (i686). Unit tests passed, with one minor nit: https://issues.apache.org/jira/browse/QPID-5449 Installed python tools, python client. Built drain spout C++ examples, all looks good. The man page has this one interesting glitch:

[Proton] Should engine allow links to be re-opened?

Hi, While playing around with the proton-c engine, I tried to re-open a link that I had previously closed. The link failed to come up - but no error state was returned. Should the engine allow a previously closed link to be re-opened? IOW, should the engine allow the following Link test to

Re: Are there standard performance/benchmark tests for proton messenger?

Hi Fraser, - Original Message - From: Fraser Adams fraser.ad...@blueyonder.co.uk To: users@qpid.apache.org Sent: Saturday, May 3, 2014 5:06:44 AM Subject: Are there standard performance/benchmark tests for proton messenger? Hey all, What sort of performance testing and

Re: dispatch router handles one million addresses

Great! Thank you for the good work, Mick - very useful indeed. - Original Message - From: Michael Goulish mgoul...@redhat.com To: users@qpid.apache.org Sent: Monday, May 5, 2014 9:30:49 AM Subject: dispatch router handles one million addresses I just had a successful test of

Re: Client APIs and AMQP 1.0 (was Re: Using the messenger API to connect to a server without sending or subscribing)

Hi Gordon, My thoughts: For Java client API I think JMS should be our primary focus. I'm quite fond of qpid::messaging. I would like to see us (QPID) continue to support this api and evolve it. For multi-language support, I think we should leverage swig as is done by Messenger today.

Re: Client APIs and AMQP 1.0 (was Re: Using the messenger API to connect to a server without sending or subscribing)

) On 05/15/2014 01:44 PM, Ken Giusti wrote: I think we should develop Messenger as an alternative client API to qpid::messaging, focusing on use cases that are not necessarily well covered by the existing qpid::messaging API. I think they complement each other nicely. In what way do

Q: change in transport behavior since 0.7

Hi, I've started hitting some pygnus negative test failures on trunk that used to pass on 0.7. There seems to have been an change to the behavior in the pn_transport_close_head() and pn_transport_close_tail() api as part of this checkin:

Re: Q: change in transport behavior since 0.7

natural place to handle a failing connection or transport object. Thoughts? - Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org Cc: users@qpid.apache.org Sent: Wednesday, August 27, 2014 3:15:23 PM Subject: Q: change in transport behavior since 0.7

Re: Q: change in transport behavior since 0.7

- Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org Cc: users@qpid.apache.org Sent: Wednesday, August 27, 2014 3:15:23 PM Subject: Q: change in transport behavior since 0.7 Hi, I've started hitting some pygnus negative test failures on trunk that used

Re: proton Messenger error handling/recovery REQUEST FEEDBACK!

I'm also interested; personally never felt comfortable with the lack of visibility regarding things like connection failures that Messenger's api currently provides. Tangentially related, perhaps - I'd like to see errors reported via the event collector interface. While my issue is engine

Re: [VOTE] Release Qpid 0.30 components

I tested a subset, see below. Testing on Centos 6 x86_64 VM, built and installed, then ran a series of Openstack oslo.messaging tests using the installed components. - Original Message - From: Justin Ross jr...@apache.org To: users@qpid.apache.org Sent: Tuesday, September 16, 2014

Re: [VOTE] Release revised 0.30 python, qmf, tests, and tools components

- Original Message - From: Justin Ross jr...@apache.org To: users@qpid.apache.org Sent: Friday, September 19, 2014 8:42:33 AM Subject: [VOTE] Release revised 0.30 python, qmf, tests, and tools components Hi, folks. The RC 1 versions of the python components were missing license

Re: Proton 0.8 RC1

I'm hitting an 'invalid read' valgrind error in the python message LoadSave tests: [kgiusti@t530 python]$ valgrind -q --trace-children=yes --suppressions=./proton_tests/valgrind.supp ./proton-test proton_tests.message.LoadSaveTest.testDataproton_tests.message.LoadSaveTest.testData

Re: Welcome Ernie Allen as a Qpid committer

Yay Ernie! - Original Message - From: Gordon Sim g...@redhat.com To: users@qpid.apache.org Sent: Friday, November 21, 2014 4:28:58 AM Subject: Welcome Ernie Allen as a Qpid committer The Qpid PMC have voted to grant commit rights to Ernie Allen in recognition of his contributions

Re: [VOTE] Approve Qpid Dispatch 0.3-rc3 as the final 0.3 release

+1 Built/installed/ran unit tests on Centos 7 x64. Set up a two node configuration and sent oslo.messaging traffic over it - all good. - Original Message - From: Ted Ross tr...@redhat.com To: users@qpid.apache.org Sent: Friday, January 9, 2015 1:19:18 PM Subject: [VOTE] Approve

Re: [VOTE] Proton 0.9 RC 2

Hate to be a party-pooper, but: 1: proton_tests.utils.SyncRequestResponseTest.test_request_response fail 1: Error during test: Traceback (most recent call last): 1: File /home/kgiusti/Downloads/qpid-proton-0.9-rc-2/tests/python/proton-test, line 355, in run 1: phase() 1:

Re: [VOTE]: Proton 0.9-rc-3

[X] Yes, release Proton 0.9-rc-3 as 0.9 final - Original Message - From: Rafael Schloming r...@alum.mit.edu To: pro...@qpid.apache.org, users@qpid.apache.org Sent: Monday, March 16, 2015 4:42:18 PM Subject: [VOTE]: Proton 0.9-rc-3 Hi Everyone, Here's a quick respin of

Re: VOTE: Release Proton 0.9-rc-1 as 0.9 final

Additionally, the following python unit tests fail unless the openssl libraries are installed: proton_tests.engine.ServerTest.testIdleTimeout proton_tests.engine.ServerTest.testKeepalive proton_tests.messenger.IdleTimeoutTest.testIdleTimeout

Re: VOTE: Release Proton 0.9-rc-1 as 0.9 final

Anyone else getting the following errors when building the docs? ;; This buffer is for notes you don't want to save, and for Lisp evaluation. ;; If you want to create a file, visit that file with C-x C-f, ;; then enter the text in that file's own buffer. Generating example index... finalizing

Re: 0.9 release schedule

wrote: On Fri, 2015-03-06 at 08:50 -0500, Ken Giusti wrote: - Original Message - From: Andrew Stitcher astitc...@redhat.com To: pro...@qpid.apache.org Sent: Monday, March 2, 2015 8:46:10 PM Subject: Re: 0.9 release schedule On Mon, 2015-03-02 at 20:00 +

Re: VOTE: Release Proton 0.9-rc-1 as 0.9 final

FWIW: pushed a fix to these doc errors: https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=bc2b630eb969710b04a861797567ab2dc368020a - Original Message - From: Ken Giusti kgiu...@redhat.com To: users@qpid.apache.org Cc: pro...@qpid.apache.org Sent: Monday, March

Re: proton application context API deprecated in 0.9?

? - Original Message - From: Rafael Schloming r...@alum.mit.edu To: users@qpid.apache.org Sent: Monday, March 9, 2015 3:10:47 PM Subject: Re: proton application context API deprecated in 0.9? On Mon, Mar 9, 2015 at 10:35 AM, Ken Giusti kgiu...@redhat.com wrote: Hi, I just

Re: proton application context API deprecated in 0.9?

- Original Message - From: Rafael Schloming r...@alum.mit.edu To: users@qpid.apache.org Sent: Tuesday, March 10, 2015 6:44:29 AM Subject: Re: proton application context API deprecated in 0.9? On Mon, Mar 9, 2015 at 4:11 PM, Ken Giusti kgiu...@redhat.com wrote: Hi Rafi - thank

Re: 0.9 release schedule

- Original Message - From: Andrew Stitcher astitc...@redhat.com To: pro...@qpid.apache.org Sent: Monday, March 2, 2015 8:46:10 PM Subject: Re: 0.9 release schedule On Mon, 2015-03-02 at 20:00 +, Gordon Sim wrote: On 03/02/2015 07:07 PM, Rafael Schloming wrote: Hi

Re: Proposed SASL changes (API and functional)

- Original Message - From: Gordon Sim g...@redhat.com To: users@qpid.apache.org Cc: pro...@qpid.apache.org Sent: Monday, March 2, 2015 2:30:28 PM Subject: Re: Proposed SASL changes (API and functional) On 02/24/2015 08:48 PM, Andrew Stitcher wrote: In a short while when people

Python 3 port is 'done'

Well, done enough to consider merging to master. While the patch is quite large, most of the changes are simple syntax changes to avoid non-python3 compliant syntax. The code is available on the kgiusti-python3 branch at the Apache repo.

Re: Python 3 port is 'done'

MessengerTests tests (all that aren't skipped) fail with Unexpected input while waiting for receiver to initialize: READY - Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org, users@qpid.apache.org Sent: Wednesday, April 29, 2015 4:05:32 PM Subject: Python

Re: Python 3 port is 'done'

- Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org Cc: users@qpid.apache.org Sent: Thursday, April 30, 2015 9:18:26 AM Subject: Re: Python 3 port is 'done' - Original Message - From: Rafael Schloming r...@alum.mit.edu To: pro

Re: Python 3 port is 'done'

- Original Message - From: Robbie Gemmell robbie.gemm...@gmail.com To: pro...@qpid.apache.org Cc: users@qpid.apache.org Sent: Thursday, April 30, 2015 10:20:07 AM Subject: Re: Python 3 port is 'done' On 29 April 2015 at 21:05, Ken Giusti kgiu...@redhat.com wrote: Well, done

Re: AMQP 1.0 and Shared Subscriptions

- Original Message - From: Ted Ross tr...@redhat.com To: pro...@qpid.apache.org Sent: Wednesday, May 6, 2015 10:25:32 AM Subject: Re: AMQP 1.0 and Shared Subscriptions On 05/06/2015 10:05 AM, Ken Giusti wrote: Bump this up. I'm essentially in the same boat

Re: Python 3 port is 'done'

and tested. I'm planning on merging this into master after the weekend unless I hear of any show stoppers. thanks, -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org, users@qpid.apache.org Sent: Wednesday, April 29, 2015 4:05:32 PM Subject: Python

Re: Python 3 port is 'done'

FYI: Python 3 support has been merged to qpid-proton master. Let us know if you hit any problems - thanks. -K - Original Message - From: Ken Giusti kgiu...@redhat.com To: pro...@qpid.apache.org, users@qpid.apache.org Cc: Flavio Percoco fla...@redhat.com Sent: Thursday, June 18

Re: Qpid C++ 0.34 alpha now available

Hi Robbie, Would it be possible to include the fix to https://issues.apache.org/jira/browse/QPID-6568 in the 0.34 release? https://svn.apache.org/r1685587 There's a nasty memory leak in proton 0.6 that can be triggered by long lived connections. We've hit that while testing qpid-dispatch.

Re: Can we release proton 0.10? Can we add Py3K to that release?

Re: py3k - I think we're really close - I've rebased my local kgiusti-python3 to latest trunk, and have a few bugs to sort out but I don't think that will take too long. The one missing 'feature' I had planned for py3: modify the tox tests to automagically run under all installed versions of

Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

Hi Matt, As you pointed out, and in case others are unaware, Darryl Pierce has created a Personal Package Archive containing various QPID packages for ubuntu users: https://launchpad.net/~qpid However, I'm not sure of Darryl's availability for keeping this up to date - which explains why

Re: Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

- Original Message - From: Matt Broadstone mbroa...@gmail.com To: Ken Giusti kgiu...@redhat.com Cc: users@qpid.apache.org, Qpid Dev d...@qpid.apache.org Sent: Wednesday, July 1, 2015 12:10:24 PM Subject: Re: Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

Re: Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

:26 AM, Ken Giusti kgiu...@redhat.com wrote: - Original Message - From: Matt Broadstone mbroa...@gmail.com To: Ken Giusti kgiu...@redhat.com Cc: users@qpid.apache.org, Qpid Dev d...@qpid.apache.org Sent: Wednesday, July 1, 2015 12:10:24 PM Subject: Re: Qpid packages

Re: Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

crap - hit send by accident. - Original Message - From: Ken Giusti kgiu...@redhat.com To: users@qpid.apache.org Cc: Qpid Dev d...@qpid.apache.org Sent: Monday, July 6, 2015 1:06:03 PM Subject: Re: Qpid packages for Ubuntu, was Re: [RESULT] [VOTE] Release Qpid CPP 0.34

Re: [VOTE] Release Qpid CPP 0.34

+1 Built installed on fedora21 using proton 0.9.1 (from testing repo) Ditto Ubuntu 14.04LTS Both passed running against the openstack amqp1.0 functional tests. - Original Message - From: Robbie Gemmell robbie.gemm...@gmail.com To: users@qpid.apache.org Sent: Thursday, June 25, 2015

Re: [VOTE] Release Qpid Proton 0.10

-1 I'm hitting a crash in this RC. It appears to be due to SASL not switching to decryption when the input buffer contains both the outcome frame and the first encrypted frame. The encrypted frame is parsed as unencrypted. see https://issues.apache.org/jira/browse/PROTON-975 - Original

Re: Proton Python binding: access to AMQP Data and Sequence encodings?

Hi Kim, The proton message object supports an 'inferred' property that lets you control this. From the python binding: inferred = property(_is_inferred, _set_inferred, doc= The inferred flag for a message indicates how the message content is encoded into AMQP sections. If inferred is true

Re: The un-reactor

- Original Message - > From: "aconway" > To: users@qpid.apache.org > Sent: Monday, October 26, 2015 12:23:01 PM > Subject: Re: The un-reactor > > On Thu, 2015-10-22 at 22:03 -0700, Cliff Jansen wrote: > > I'm not sure if this exactly fits your question (especially

Re: Proton 0.11.0 unresolved issues

Re: PROTON-905 I think this needs to be pushed off until next release. I personally don't feel it's actually a critical priority. See my comment

[RESULT] [VOTE] Use semantic versioning for the qpid-cpp components

/browse/QPID-6857 - Forwarded Message - > From: "Ken Giusti" <kgiu...@redhat.com> > To: "Qpid Dev" <d...@qpid.apache.org> > Sent: Tuesday, November 10, 2015 10:23:44 AM > Subject: [VOTE] Use semantic versioning for the qpid-cpp component

Re: [VOTE] Release Qpid Proton 0.11.0

+1 Tested: unit tests pass (Fedora 22 workstation) pyngus unit tests and examples pass, both py3 and py2 oslo.messaging functional and drivers pass, both py3 and py2 oslo-messaging-clients smoketest pass - Original Message - > From: "Justin Ross" > To:

  1   2   3   4   >