Re: [VOTE] Release Qpid Interop Test 0.3.0

+1. I built to a local prefix and ran all the tests against the router. I found one build-related issue, https://issues.apache.org/jira/browse/QPIDIT-144, which is not a blocker for the release. On Thu, Oct 28, 2021 at 4:31 PM Kim van der Riet wrote: > Hi, > > I have assembled a release of

Re: AMQP footer

Hi, Thomas. In a word - and so there's no mystery about the status - it's simply not implemented yet. On Mon, Jul 19, 2021 at 6:50 AM Thomas Kettenbach wrote: > Hi all, > > i am puzzled about the support for AMQP Footers in qpid-proton. We're > currently thinking about a use case, where we

Re: Outreachy Applicant

o provide any additional information after you save your final > application. > > > If you have any suggestions or guidance please let me know. > > > Best regards, > Rakhi > > On Wed, Mar 31, 2021 at 7:09 PM Rakhi Kumari wrote: > >> Thanks!! I will take a look

Re: Outreachy Initial Applicant

Hi, Ankita. We're very happy to have you! To get things started: do you have your dev environment to the point where you can build Proton C and run the tests? On Thu, Apr 1, 2021 at 2:15 AM Ankita wrote: > Hi guys, > > I'm Ankita. I'm an outreachy initial applicant. > With an intermediate

Re: Outreachy Applicant

Hi, Saakshi. Great! You seem to be off to a good start. Do you have the Proton C code building and tests running? On Thu, Apr 1, 2021 at 1:35 AM Saakshi Jain wrote: > Hi everyone! > > I am Saakshi Jain and will be participating as the Outreachy initial > applicants. I'm quite excited to make

Re: Apache

Hi, Sree. It's great to see you here! To get things started, do you have a working dev environment, where you can build the Proton C code and run the tests? https://github.com/apache/qpid-proton/blob/main/INSTALL.md There's also recently been some helpful discussion about getting started on

Re: Outreachy applicant 2021

; Does it mean that finally there will be only one intern for Apache? > > On Thu, 1 Apr 2021, 22:15 Justin Ross, wrote: > > > Hi, Sushma. We are very happy to have you here! > > > > I was anticipating taking just one intern from the set of applicants. > > Apache as a w

Re: Outreachy Applicant

Shivani, if you're already set to start, here's a task to look at: https://issues.apache.org/jira/browse/PROTON-2364 On Thu, Apr 1, 2021 at 12:26 PM Justin Ross wrote: > Hi, Shivani. Have you been able to build Proton C and run the tests? > > On Wed, Mar 31, 2021 at 10:52 PM Shiv

Re: Outreachy applicant 2021

Hi, Sushma. We are very happy to have you here! I was anticipating taking just one intern from the set of applicants. Apache as a whole has eight internship opportunities, but I thought they would be distributed across multiple Apache projects. Strangely, so far Qpid is the only project listed.

Re: Outreachy Applicant

Hi, Shivani. Have you been able to build Proton C and run the tests? On Wed, Mar 31, 2021 at 10:52 PM Shivani Singh wrote: > Hello, I am also an Outreachy Applicant. I have set up the required > environment and I use linux. > Can you suggest some good issues that I can work on? > Thank you! >

Re: outreachy applicant

Ah! Rakhi ninjaed me. ;) On Wed, Mar 31, 2021 at 12:17 PM Justin Ross wrote: > Here's the sequence I use: > > - cd qpid-proton > - mkdir bld > - cd bld > - cmake .. -DCMAKE_BUILD_TYPE=Coverage > - make build > > You don't need the CMakeLists.txt file where

Re: outreachy applicant

XX and ran the command but there > seems to be no output > > On Wed, Mar 31, 2021 at 7:45 PM mehaboob shariff > wrote: > > > Tahnk you Justin, will get back to you if I face any troubles > > > > On Wed, Mar 31, 2021 at 6:59 PM Justin Ross > wrote: > > >

Re: Outreachy Applicant | Joining the Qpid Team

task >> >> Appreciate your time. >> >> Warm regards >> >> On Tue, Mar 30, 2021 at 6:25 PM Justin Ross wrote: >> >>> Hi, Sunday. I'm very glad to have you involved! Have you been able to >>> check out and build Qpid Proton C on your machine? >&g

Re: outreachy applicant

Hi, Mehaboob. Here's one to try: https://issues.apache.org/jira/browse/PROTON-2358 Please tell us about any obstacles you face. On Tue, Mar 30, 2021 at 4:56 PM mehaboob shariff wrote: > okay, thank you for the information > > On Wed, Mar 31, 2021 at 2:08 AM Justin Ross wrote: > &

Re: Outreachy Applicant

Hi, Rakhi. Here's an issue to try out: https://issues.apache.org/jira/browse/PROTON-2357 Please let us know about any trouble you encounter. On Tue, Mar 30, 2021 at 3:14 PM Justin Ross wrote: > Rakhi, excellent! You are off to a great start. I'm looking for a good > issue to get s

Re: Getting started with contributing to Apache Qpid

Linux dev environment. Can you provide me with the > > steps > > > to > > > > > get the Proton C code to build? > > > > > > > > > Please take a look here - > > > > https://github.com/apache/qpid-proton/blob/master/INSTALL.md > > &

Re: outreachy applicant

e repo successfully > > > On Wed, Mar 31, 2021 at 12:51 AM Justin Ross > wrote: > > > Okay, next is to use git to fetch the Qpid Proton C source repo and get > it > > building. > > > > The instructions are here: > > https://github.com/apache/qpid-proton/b

Re: outreachy applicant

12:07 AM Justin Ross > wrote: > > > Hi, Mehaboob. I spoke to you in private email as well. What kind of > > development environment do you have? > > > > On Tue, Mar 30, 2021 at 11:44 AM mehaboob shariff > > > wrote: > > > > > Hello this is M

Re: Outreachy Applicant

Rakhi, excellent! You are off to a great start. I'm looking for a good issue to get started with - I'll report back. On Tue, Mar 30, 2021 at 1:56 PM Rakhi Kumari wrote: > Hi everyone!! > > I am an Outreachy 2021 summer applicant. I am also an open source > enthusiast and previously I have

Re: outreachy applicant

Hi, Mehaboob. I spoke to you in private email as well. What kind of development environment do you have? On Tue, Mar 30, 2021 at 11:44 AM mehaboob shariff wrote: > Hello this is Mahaboob Shariff a CS undergrad. I would like to participate > in the apache community for the outreachy intern. >

Re: Outreachy Applicant

Hi, Agha. That's what we're seeing as well. Do you have some experience with C++? On Tue, Mar 30, 2021 at 10:25 AM Agha Saad wrote: > Hi, this is Agha Saad from Pakistan. My initial application for Outreachy > got approved. I am interested in contributing to the Apache community. Is > there

Re: Getting started with contributing to Apache Qpid

Hi, Kajal. You have the right forum, and we're happy to have you! To get things started, do you have a Linux dev environment? If you do, the next step after that is to get the Proton C code to successfully build. On Tue, Mar 30, 2021 at 5:37 AM Kajal_Sah 19MCA17 wrote: > Dear developers, > >

Re: Proton CPP - Set dynamic node properties

HBergeron, would you raise an improvement request for this? I searched, and I didn't find an existing issue for it. https://issues.apache.org/jira/secure/CreateIssue!default.jspa?pid=12313720 On Tue, Dec 1, 2020 at 12:08 PM Robbie Gemmell wrote: > I would guess they should be exposed via

Re: Qpid Proton Python - waiting for data from external process

In case it's still useful, an example of creating an anonymous sender (used here for the response part of a request/response interaction): https://github.com/amqphub/equipage/blob/master/qpid-proton-python/respond.py#L44 (define the anonymous sender)

Re: C++ Client - loading certificate from memory

Based on my reading of the API docs, I don't see anything that makes me believe this is currently possible: http://qpid.apache.org/releases/qpid-proton-0.30.0/proton/cpp/api/classproton_1_1ssl.html

Re: An imperative AMQP client API

I like to think of the message as a pure value object. As a result, it can have whatever lifecycle the API user chooses. For me, that's a reason to isolate it from the delivery and tracker, because they do have more tightly defined lifecycles. If there was a substantial win in convenience, I

An imperative AMQP client API

Hi, everyone. For a while now, some members of the Qpid community have been working on a new style of messaging API. It now has a reasonable shape, and we want to share it and get your feedback. We currently offer either JMS or Proton's reactive API. These certainly aren't going anywhere -

An imperative AMQP client API

Hi, everyone. For a while now, some members of the Qpid community have been working on a new style of messaging API. It now has a reasonable shape, and we want to share it and get your feedback. We currently offer either JMS or Proton's reactive API. These certainly aren't going anywhere -

Re: Restrict TLS Versions and Ciphers using qpid proton-cpp API

I also took a look, and I don't think we have accessors for these in C++. I raised a ticket for it: https://issues.apache.org/jira/browse/PROTON-2139 On Thu, Oct 24, 2019 at 7:21 AM Gordon Sim wrote: > On 18/10/2019 3:11 pm, bajanfella wrote: > > I see that there is a

Re: Set destination from Qpid Proton Client

This still looks like a normal receive scenario to me. Since you've created the queue using the REST API, all you need to do is use the name of the queue in your client code: https://github.com/ssorj/equipage/blob/master/qpid-proton-python/receive.py#L40 - self.address here would be the name of

Re: Unexpected error from qpidd-cpp 1.39 when queue is faulty

Kim? On Tue, May 14, 2019, 14:01 Gordon Sim wrote: > On 14/05/2019 10:46 am, Pål Skjager Løberg wrote: > > For a client, just getting "illegal-argument: Value for replyText is too > > large" back as an error when sending is not the most useful info and I > > suspect, especially after reading

Re: [VOTE] Release Apache Qpid Proton 0.27.0

+1. I tested on Fedora 29 x64 using quiver and qtools. There were no test failures for me. On Wed, Feb 6, 2019 at 6:02 AM Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a Qpid Proton 0.27.0 release, please > give it a test out and vote accordingly. > > The files can be

Re: Drain issue in proton C++

Hi, Ali. We're currently planning to kick off a release in the first week of February. On Mon, Jan 21, 2019 at 6:09 AM HADI Ali wrote: > Hello, > > Do you have an idea when Proton 0.27 is planned to be released ? > We are particularly interested in the drain issue. > > Thanks, > Ali > >

[ANNOUNCE] Apache Qpid C++ 1.39.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid C++ 1.39.0. Apache Qpid (https://qpid.apache.org) is a cross-platform messaging solution that implements the Advanced Message Queuing Protocol (AMQP, https://www.amqp.org). It provides message brokers

[RESULT] [VOTE] Release Apache Qpid C++ 1.39.0

The release is approved with 5 votes in favor and none against. I'll move the artifacts to the release dist location. On Monday, I'll push the site update and send the announcement. On Mon, Oct 22, 2018 at 5:47 AM Justin Ross wrote: > Hi, everyone. Please test this release candidate and v

[VOTE] Release Apache Qpid C++ 1.39.0

Hi, everyone. Please test this release candidate and vote based on what you find. Source archive and signatures: https://dist.apache.org/repos/dist/dev/qpid/cpp/1.39.0-rc1/ Issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12342978 Tag: 1.39.0-rc1

Re: [VOTE] Release Apache qpid-interop-test 0.2.0 (RC2)

I can confirm that I see the same issue with RC3. On Wed, Aug 1, 2018 at 5:42 AM Justin Ross wrote: > I just discovered I missed the RC3. I'll try again with that. > > On Wed, Aug 1, 2018 at 5:41 AM Justin Ross wrote: > >> In my testing, QIT 0.2 rc2 is generating a build/

Re: [VOTE] Release Apache qpid-interop-test 0.2.0 (RC2)

I just discovered I missed the RC3. I'll try again with that. On Wed, Aug 1, 2018 at 5:41 AM Justin Ross wrote: > In my testing, QIT 0.2 rc2 is generating a build/config.sh that has > python2.7 libraries in the PYTHON3PATH. I don't have any preexisting > PYTHONPATH or PYTHON3PATH. &

Re: [VOTE] Release Apache qpid-interop-test 0.2.0 (RC2)

In my testing, QIT 0.2 rc2 is generating a build/config.sh that has python2.7 libraries in the PYTHON3PATH. I don't have any preexisting PYTHONPATH or PYTHON3PATH. [jross@localhost ~]$ echo $PYTHON3PATH

Re: [VOTE] Release Apache Qpid Proton 0.24.0

+1. Built on Fedora 26. Built Dispatch against it. Ran the Proton and Dispatch tests (no failures). Ran Qpid JMS 0.24.0 RC1 against it in some benchmarks, both peer to peer and client server with Dispatch. On Tue, Jun 26, 2018 at 7:56 AM Robbie Gemmell wrote: > Hi folks, > > I have put

Re: [VOTE] Release Apache Qpid JMS 0.34.0

+1. Built from source and ran the tests (no failures). Tested the maven artifacts in some quiver benchmark runs against artemis master and dispatch 1.1.0. On Tue, Jun 26, 2018 at 11:09 AM Gordon Sim wrote: > On 25/06/18 21:11, Robbie Gemmell wrote: > > Hi folks, > > > > I have put together a

Re: [dispatch] Seeking comments before landing a change to the docs tree

Yes, I will. Thanks! On Tue, Jun 26, 2018 at 6:07 AM Ted Ross wrote: > On Tue, Jun 26, 2018 at 8:32 AM, Justin Ross > wrote: > > https://github.com/apache/qpid-dispatch/pull/296 > > > > Ted, Ganesh, is this okay to merge? > > Yes,

[dispatch] Seeking comments before landing a change to the docs tree

https://github.com/apache/qpid-dispatch/pull/296 Ted, Ganesh, is this okay to merge?

Re: Seeking opinions: Change to proton-c SASL mechanisms semantics

at 12:46 PM Gordon Sim wrote: > On 15/06/18 20:40, Justin Ross wrote: > > On Fri, Jun 15, 2018 at 12:25 PM Robbie Gemmell < > robbie.gemm...@gmail.com> > > wrote: > > > >> I think its reasonable that clients dont attempt to do GSSAPI by > >> defau

Re: Seeking opinions: Change to proton-c SASL mechanisms semantics

On Fri, Jun 15, 2018 at 12:25 PM Robbie Gemmell wrote: > I think its reasonable that clients dont attempt to do GSSAPI by > default unless it has been enabled in some way, since it requires > specific external configuration. > This is the case that interests me. I've been tripped up by this

Re: Proposed Feature Removal from Dispatch Router

On Tue, Apr 17, 2018 at 9:10 AM Gordon Sim wrote: > I think Ted is right that the feature did not reach that goal. It is not > sufficiently clear what is going on and on balance doesn't I think > justify the potential annoyance. > > However I do think that some other solution to the problem of

Re: Using qpid in a JEE container

Hi, Leor. Here's one example. It's based on WildFly Swarm, but you can map it back to JBoss XML pretty easily. https://github.com/ssorj/upstate/tree/master/worker-swarm https://github.com/ssorj/upstate/blob/master/worker-swarm/container/src/main/java/org/amqphub/upstate/swarm/SwarmWorker.java

Re: Build QPID C++ Using Visual Studio 2013 on Windows 10

Following up on a few things here, QPID-8155 is now fixed. After that I encountered and fixed another build failure in QPID-8169. https://issues.apache.org/jira/browse/QPID-8155 https://issues.apache.org/jira/browse/QPID-8169 Apache Infra setup a Windows CI job for us. It's now linked from the

Re: Proton C source reorg and removal of deprecated or obsolete code

12, 2018 at 12:14 PM, Justin Ross <justin.r...@gmail.com> > wrote: > > > > src/messenger still there - oversight, or do we need to hold onto this? > > > > > > > It's still used by one of the test tools. > > > > > We can replace msgr-send.

[ANNOUNCE] Apache Qpid C++ 1.38.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid C++ 1.38.0. Apache Qpid (https://qpid.apache.org) is a cross-platform messaging solution that implements the Advanced Message Queuing Protocol (AMQP, https://www.amqp.org). It provides message brokers

[RESULT] [VOTE] Release Apache Qpid C++ 1.38.0

The vote has passed with 6 votes in favor and none against. I will stage the artifacts today and update the website once they propagate to the mirrors. On Thu, Mar 22, 2018 at 5:33 AM, Justin Ross <justin.r...@gmail.com> wrote: > Hi, all. Please test this release candidate and indi

Re: [VOTE] Release Apache Qpid C++ 1.38.0

+1 Validated signature and checksum. Ran the tests on Fedora 26 x86-64. On Thu, Mar 22, 2018 at 5:33 AM, Justin Ross <justin.r...@gmail.com> wrote: > Hi, all. Please test this release candidate and indicate your vote on > this thread. > > Source archive and s

Re: qpid-proton cpp - Wrong auth with reconnect options lead to error : Too many reconnect attempts

Hi, Baptiste. There's something coming soon in Proton C 0.22.0 that may help with that. https://issues.apache.org/jira/browse/PROTON-1589 This is on master now, and the 0.22.0 release process will start this month. On Fri, Mar 23, 2018 at 7:57 AM, Baptiste Robert

Re: qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

Alex, with the following change now on master, the pkg-config based build is working for me. https://github.com/apache/qpid-cpp/commit/f14f1bc162c4f4249d6397cbf1ee2522074dc17a On Mon, Mar 19, 2018 at 2:20 PM, Justin Ross <justin.r...@gmail.com> wrote: > Seems likely that it's th

Re: qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

Seems likely that it's this change of mine. https://github.com/apache/qpid-cpp/commit/b18583a6c05d0bb8cb9502f0823d902e17b2410e I'll try to reproduce and see if this really the cause. On Mon, Mar 19, 2018 at 12:28 PM, Robbie Gemmell wrote: > I see the same thing on

Build failure in Qpid C++ legacystore tests

I'm seeing this when I enable legacystore. https://gist.github.com/ssorj/f9320463cb0c5f3318b0226577b5e305 [ 87%] Building CXX object src/tests/legacystore/CMakeFiles/jtt.dir/jrnl/jtt/test_case_result.cpp.oIn file included from /usr/include/boost/test/test_tools.hpp:45:0, from

Upcoming C++ and Python releases

Hi, all. I'm starting work on new releases of the C++ and Python components. Let me know if there's something in particular you would like to do before I cut a release candidate.

Re: Proton C source reorg and removal of deprecated or obsolete code

On Mon, Mar 12, 2018 at 8:57 AM, Alan Conway wrote: > Overall it's good. > > Things to consider - none are essential: > > drop 'binding/', put the language bindings directly in the root dir. It's > pretty obvious what they are - ruby, go, cpp etc. > > Possibility: a "c" or

Proton C source reorg and removal of deprecated or obsolete code

Hi, all. After we split Proton J out of Proton, the existing Proton C source tree no longer made sense. This proposed change moves the proton-c/* content to the top level and generally aligns the source tree with conventions we use in some of our other code bases. It also removes bindings,

Re: WARNING: proton ruby package and gem name change

I don't feel very strongly about doing it or not doing it. If we are going to do it, however, this is good timing, since we'll be removing Messenger in the same release. Users who want to carry on with the existing API would continue with the older releases and package name. On Fri, Mar 2, 2018

Re: C++ imperative client API

Hi, Olivier. It's still in prototype and research mode. We don't have anything like a design proposal yet. I hope we'll have more time to work on it soon. When we have some concrete design points and sample code for evaluation, we'll share it here so we can have an open design discussion. On

Re: Qpid PPA releases for qpid-cpp-1.37/qpid-proton-0.18

On Thu, Feb 1, 2018 at 4:58 AM, Chris Richardson wrote: > Could we please have an update to the very useful PPA at > https://launchpad.net/~qpid/+archive/ubuntu/released? It would be really > useful to have qpid-cpp-1.37 and qpid-proton-0.18 in there. > > I realise I mentioned

Re: New user questions: Broker/AMQP versions

On Mon, Jan 22, 2018 at 6:05 AM, gewesp wrote: > Hi all, > > I'm consulting with a company in the security business and we're evaluating > the use of QPID as a messaging platform. > > Q1: Supported AMQP versions of the C++ broker (qpidd): > * According to

Re: How can clients create a queue using AMQP 1.0?

Here's an example in Qpid Proton C++. https://github.com/ssorj/messaging-examples/blob/master/qpid-proton-cpp/subscriptions/durable-subscribe.cpp On Thu, Nov 30, 2017 at 10:48 AM, tomt wrote: > have it survive across a reconnect? > Gordon Sim wrote > > On 30/11/17 18:22,

Re: Need help compiling in Visual Studio QPID C++

Hi, Paul. What are the errors you are seeing? I gave it a try on AppVeyor, and I immediately ran into a problem with a newer version of msbuild. https://ci.appveyor.com/project/ssorj/qpid-cpp/build/1.0.13 Chuck, what does that portend? Do we need to generate new build metadata for Windows?

Re: [VOTE] Release Qpid Broker-J 7.0.0 (RC2)

As an aside, switching the other Qpid components to use archive names of the form apache-qpid-- works for me. I'd like if things were a bit neater in this regard. On Tue, Nov 7, 2017 at 9:22 AM, Robbie Gemmell wrote: > Keeping the maven artifactId the same makes

Seeking help with some Qpid C++ issues

Hi, all. I've been attempting to get Qpid C++ in shape for a release. I need some review for some of the changes I've proposed (got some already from Robbie - thanks) and some help with test failures. The change that needs particular review attention:

Re: Ruby Qpid Proton Gem release

We're still trying for end of September, but it's now looking tight, so it may slip to early October. On Tue, Sep 19, 2017 at 11:11 AM, Gregor Berginc wrote: > Dear all, > > I hope this is the right place to ask about the planned releases. I have > integrated Qpid

Re: qpid-python-test.bat does not exist

https://issues.apache.org/jira/browse/QPID-7833 On Thu, Jun 22, 2017 at 12:20 PM, Justin Ross <justin.r...@gmail.com> wrote: > Hey, Greg. Good find. It's missing from the source distribution. > > To work around this, you can fetch this file and place it next to > qpid-pyth

Re: qpid-python-test.bat does not exist

Hey, Greg. Good find. It's missing from the source distribution. To work around this, you can fetch this file and place it next to qpid-python-test: https://raw.githubusercontent.com/apache/qpid-python/1.36.x/qpid-python-test.bat On Thu, Jun 22, 2017 at 11:02 AM, Greg Oliver

Re: cpp broker not respecting max-queue-count ?

The source is authoritative, but: https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP It may be out of date, but it has descriptions. On Mon, May 8, 2017 at 4:20 PM, Gordon Sim wrote: > On 08/05/17 15:55, Chester wrote: > >> Is there a doc somewhere that

Re: [DISCUSS] Migrate Qpid Broker for Java and Qpid JMS AMQP 0-x Client from SVN to GIT

I like qpid-broker-j best of the alternatives proposed. I think qpid-broker alone will cause a little confusion. On Mon, Mar 27, 2017 at 3:41 AM, Rob Godfrey wrote: > On 27 March 2017 at 12:35, Robbie Gemmell > wrote: > > > On 27 March 2017

Re: Corrupt artifacts on Qpid release web page

On Mon, Mar 20, 2017 at 6:59 AM, Adel Boutros wrote: > Could the issue be I am behind a proxy? > Yeah, that could definitely do it. The lua closer script uses a path that looks like just another file. If the proxy isn't forwarding the ultimate target's content type, it

Re: Corrupt artifacts on Qpid release web page

On Mon, Mar 20, 2017 at 6:26 AM, Rob Godfrey wrote: > On 20 March 2017 at 14:23, Adel Boutros wrote: > > > Hello Rob, > > > > > > I just saw your mail and I confirm what you propose works correctly. I > > opened your link via chrome and it

Re: [DISCUSS] Drop 0-10 based JCA/RA artefacts from Qpid JMS 0-x Client.

+1. Thanks for raising this, Keith. On Sun, Mar 19, 2017 at 3:54 PM, Keith W wrote: > Hi all, > > I'd like to propose that we drop the AMQP 0-10 based JCA (J2EE > Connector Architecture) and RA (Resource Adaptor) artefacts from the > next major Qpid JMS 0-x Client release

[RESULT] [VOTE] Release Qpid Python 1.36.0

The vote has passed with 4 binding votes and 1 non-binding. I'll setup the artifacts for distribution right away and update the website once they are propagated to the mirrors.

Re: [VOTE] Release Qpid Python 1.36.0

+1 I tested install and ran the test suite against recent qpidd master on Fedora 25. On Tue, Mar 7, 2017 at 10:24 AM, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > On 6 March 2017 at 11:08, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > On 4 March 2017 at 01:33,

Re: Jira components

Er, correction. -legacy -> -legacy-jmx-console On Tue, Mar 14, 2017 at 10:11 AM, Justin Ross <justin.r...@gmail.com> wrote: > Here's the updated list of components. > > https://issues.apache.org/jira/browse/QPID/?selectedTab= > com.atlassian.jira.jira-projects-plugin:compon

Re: Jira components

On Mon, Mar 13, 2017 at 4:48 PM, Keith W <keith.w...@gmail.com> wrote: > On 13 March 2017 at 15:06, Rob Godfrey <rob.j.godf...@gmail.com> wrote: > > On 13 March 2017 at 15:34, Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > > > >> On 13 March 2017

Re: Jira components

On Mon, Mar 13, 2017 at 8:06 AM, Rob Godfrey wrote: > Given the restructure of the Java codebase, I'd suggest that maybe we'd > want to cut down the Java components to simply Java Broker and AMQP 0-x JMS > client and that all other components simply be turned into

Re: Jira components

Here's the updated list of components. https://issues.apache.org/jira/browse/QPID/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel On Mon, Mar 13, 2017 at 6:28 AM, Justin Ross <justin.r...@gmail.com> wrote: > There are some components that I'd like us to consider

Re: [DISCUSS] release checksum filename extension

I will change the qpid-python .sha file to SHA-512. And I wouldn't have objected to using .sha512 if Robbie had felt like going against the grain. FWIW, before I made the change to SHA-256 and .sha, I tested that Fedora's 'shasum' does not require extra options to check such files. It seems to

[VOTE] Release Qpid Python 1.36.0

Hi, everyone. This our first release candidate for the Qpid Python 1.36.0 release. Please test in your environment, report what you find, and then vote to approve or reject the release. Source distribution: https://dist.apache.org/repos/dist/dev/qpid/python/1.36.0-rc1/ Tag:

Planning for an upcoming Qpid Python release

Hi, everyone. I plan to start the process in about a week. Current issues: https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20qpid-python-1.36.0%20AND%20project%20%3D%20QPID Candidate issues:

Re: Reconnect and amqp:connection:forced

On Fri, Feb 10, 2017 at 6:53 AM, Gordon Sim wrote: > > >> The one that springs to mind is something that is intentionally removed >> from service and definitely will not return. >> > > There are other more specialised error conditions, e.g. > amqp:resource-deleted, or maybe

Re: Reconnect and amqp:connection:forced

On Fri, Feb 10, 2017 at 6:44 AM, Rob Godfrey wrote: > > Zooming out, would it make sense to eventually introduce in AMQP an > > explicit "go away, don't reconnect" variant of connection error? > > > > > What would the use case be? What would the client do in this case

Reconnect and amqp:connection:forced

http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-connection-error """ connection-forced: An operator intervened to close the connection for some reason. The client could retry at some later date. """ Do we interpret this to mean that clients should use their

Re: [VOTE] Release Qpid Proton 0.16.0

I think it's okay to proceed without the core lib in the install result. On Mon, Dec 12, 2016 at 4:35 AM, Robbie Gemmell wrote: > While looking into what might be involved to fix the install issue, I > found that Andrew actually noticed and corrected it on Thursday, >

Re: Valid values for x-declare, x-subscribe, x-binding?

Some related resources, in case your web searches didn't find them. https://cwiki.apache.org/confluence/display/qpid/Addressing+Examples https://cwiki.apache.org/confluence/display/qpid/Qpid+extensions+to+AMQP On Fri, Nov 18, 2016 at 12:29 PM, Gary Taylor wrote: > In the docs,

Re: Heads-up: Splitting proton-c into multiple libraries [Was: Proton's road ahead]

On Fri, Nov 11, 2016 at 8:46 AM, Andrew Stitcher wrote: > > Extra (potential) library: All source in directory > - extra > Could we avoid having this extra library if we copied the URL parser to the C++ binding? You noted elsewhere that the only other thing in here, the

Proton's road ahead

Hi, everyone. I’m writing this to give you all a clearer picture of our intentions for Apache Qpid Proton and to invite your feedback. There are several moving parts, so I’ll take them in turn. Messenger and Proton APIs. The Messenger API has been a source of trouble for us for a long time.

Proton Python on_sendable behavior

https://gist.github.com/ssorj/1ccf4d1499563722bc419f1e1fac11bf In this example, there is still ample credit on the link after the last on_sendable() is printed, but on_sendable is never fired again. Is that expected behavior? It appears that on_link_flow is only fired when link credit is

Qpid C++ broker - --no-data-dir and linearstore

https://gist.github.com/ssorj/d32f619dcf1cb0a462bf95a97b907cad I think this behavior is new since 0.34. It strikes me as wrong that the broker won't start - when I've explicitly selected --no-data-dir - if I have the linearstore module in the modules dir. Would it be better to have linearstore

Re: Help! ->qpid::Exception what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116): QPID - 6416?

On Wed, Sep 21, 2016 at 8:16 AM, Flores, Paul A. wrote: > The release notes for 0.32 do not list any of the bug fixes that were > fixed in 0.31. Which release notes are you looking at? I see QPID-6416 (fixVersion = 0.31) in the release notes here:

[ANNOUNCE] Apache Qpid C++ 1.35.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid C++ 1.35.0. Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise messaging solution which implements the Advanced Message Queuing Protocol (AMQP, http://www.amqp.org). It provides message

[RESULT] [VOTE] Release Qpid C++ 1.35.0

The release is approved with six binding votes in favor and none against. On Thu, Sep 1, 2016 at 4:19 AM, Justin Ross <justin.r...@gmail.com> wrote: > +1 > > I tested on Windows 10, Fedora 23, and Fedora 24. Windows had the same > long-standing test failures. > > >

Re: [VOTE] Release Qpid C++ 1.35.0

+1 I tested on Windows 10, Fedora 23, and Fedora 24. Windows had the same long-standing test failures. On Fri, Aug 26, 2016 at 4:18 PM, Justin Ross <justin.r...@gmail.com> wrote: > The artifacts proposed for release: > > https://dist.apache.org/repos/dist/dev/qpid/cpp/1.35.0

[ANNOUNCE] Apache Qpid Python 1.35.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Python 1.35.0. Qpid Python includes an AMQP messaging library and a suite of tests for AMQP conformance. This release incorporates a number of defect fixes and enhancements. Release notes are available at:

[ANNOUNCE] Apache Qpid Proton 0.14.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Proton 0.14.0. Qpid Proton is an AMQP 1.0 messaging library. It can be used in a wide range of messaging applications including brokers, clients, routers, bridges, proxies, and more. This release

Re: released outcome

On Mon, Aug 29, 2016 at 10:07 AM, Matt Broadstone <mbroa...@gmail.com> wrote: > On Mon, Aug 29, 2016 at 12:43 PM, Justin Ross <justin.r...@gmail.com> > wrote: > > > On Aug 29, 2016 06:31, "Matt Broadstone" <mbroa...@gmail.com> wrote: > > >

  1   2   3   4   >