[VOTE] Release Qpid Proton 0.13.1

Hi, folks. Here is an RC for 0.13.1. Please test and place your vote. Source distribution: https://dist.apache.org/repos/dist/dev/qpid/proton/0.13.1-rc/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheqpid-1082 Changes since 0.13.0:

[SECURITY] CVE-2016-4974: Apache Qpid: deserialization of untrusted input while using JMS ObjectMessage

[CVE-2016-4974] Apache Qpid: deserialization of untrusted input while using JMS ObjectMessage Severity: Moderate Vendor: The Apache Software Foundation Versions Affected: Qpid AMQP 0-x JMS client 6.0.3 and earlier Qpid JMS (AMQP 1.0) client 0.9.0 and earlier Description: When applications call

[ANNOUNCE] Apache Qpid Java 6.0.4 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java 6.0.4. This release addresses vulnerability CVE-2016-4974 and incorporates a number of defect fixes and enhancements. The release is available now from our website:

[ANNOUNCE] Apache Qpid JMS 0.10.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid JMS 0.10.0. This is the tenth release of our newer AMQP 1.0 JMS client, based around the Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS. This release addresses

Re: Issue when using CMake to install Qpid broker

Have you tried feeding CMake an install dir? Make one and then also specify -DCMAKE_INSTALL_PREFIX= on the cmake command line. Lately I *always* build with an install folder because that's where Qpid picks up Qpid Proton and AMQP 1.0 support - through a shared install folder. Here's a

Re: modified outcome with undeliverable-here

Hi, Matt. Contrary to the target I discussed here, I haven't completed the alphas this week. I've done the groundwork for them, but I'm waiting for the git migration to complete before I produce the final alphas. I'm away for a week, so I'll be producing them instead the week of the 11th. On

Issue when using CMake to install Qpid broker

I'm currently going through the process of installing the Qpid broker on Windows. I've already installed cmake, boost, and python and I've added the environmnet variable for the root of the Boost directory. I'm now at the step where Qpid client is to be build from a source distribution (Visual

Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue without specify a binding key

Just to be clear, AMQP 0-10 *requires* that a binding key is used to uniquely identify every binding between an exchange and a queue. It does allow for the fact that the binding may be the empty string, however only one binding per queue may use this binding key on the given exchange. So I don't

RE: [Qpid Java Broker] Cannot bind fanout exchange to a queue without specify a binding key

Thank you Keith, Issue raised: https://issues.apache.org/jira/browse/QPID-7339 Adel > From: keith.w...@gmail.com > Date: Fri, 1 Jul 2016 16:43:42 +0100 > Subject: Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue > without specify a binding key > To: users@qpid.apache.org > > Hi

RE: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Thank you Jirik and Ganesh, I will use a workaround from my side while waiting for the official release of 0.7.0 and fixes of the jira issues mentioned. Regards, Adel > From: jda...@redhat.com > Date: Fri, 1 Jul 2016 17:35:31 +0200 > Subject: Re: [Qpid-Dispatch] qdmanage query doesn't take

Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue without specify a binding key

Hi Adel Yes, this is a defect in the Web Management Console (the UI). The UI should not be demanding a binding key in this case. For the fanout exchange, the binding is simply one between exchange and queue. Actually, underneath the binding key field is used to name the Binding entity that

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Hello Adel, On Fri, Jul 1, 2016 at 5:23 PM, Adel Boutros wrote: > I have one more question: What is considered a "Management entity"? > > I have a feeling the "READ" only works with the "connector" type because > with the other types, I am getting some weird exceptions: >

RE: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

PS: If I remove the "s" from "autoLinks", I get: bash$ qdmanage -b amqp://localhost:10452 read --type=autoLink ConnectionException: Connection amqp://localhost:10452/$management disconnected > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: RE: [Qpid-Dispatch] qdmanage query

RE: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

I have one more question: What is considered a "Management entity"? I have a feeling the "READ" only works with the "connector" type because with the other types, I am getting some weird exceptions: bash$ qdmanage -b amqp://localhost:10452 read --type=connector BadRequestStatus: No name or

RE: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Thank you Ganesh, Indeed the "read" operation is working with the "--name" option. Regards, Adel > Date: Fri, 1 Jul 2016 10:33:05 -0400 > From: gmur...@redhat.com > To: users@qpid.apache.org > Subject: Re: [Qpid-Dispatch] qdmanage query doesn't take into account the > name option when passed >

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Link to the Management spec draft - https://www.oasis-open.org/committees/download.php/54441/AMQP%20Management%20v1.0%20WD09 - Original Message - > From: "Ganesh Murthy" > To: users@qpid.apache.org > Sent: Friday, July 1, 2016 10:26:46 AM > Subject: Re:

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Friday, July 1, 2016 9:00:53 AM > Subject: [Qpid-Dispatch] qdmanage query doesn't take into account the name > option when passed > > Hello, > > Using qpid-dispatch 0.6.0, I have

[Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Hello, Using qpid-dispatch 0.6.0, I have noticed that qdmanage's query operation doesn't seem to take the "--name" option if passed. Only the type option is working. As you can see from the example below, although I search for an absent entity named "localhost.broker.10253.connector", I end up

Qpid JMS: client inactivity problem

Hi people, I have another problem with Service Bus and Qpid JMS 0.9.0. The broker uses 4 minutes idle timeout. With the sample code in the examples, I verified that the client sends the first empty frame exactly 4 minutes after the consumer has connected. After that, Qpid sends an empty frame

[RESULT] [VOTE] Release Qpid Java 6.0.4

There were 6 binding +1 votes, and no other votes received. The vote has passed. I will add the archives to the dist release repo and release the maven staging repo shortly. The website will be updated later after the artifacts have had time to sync to the mirrors and maven central.