Re: Qpid Dispatch Router 0.5 RC1

Hi Ted, I gave the RC1 a try and it seems that I'm now unable to connect to the qpidd broker using SASL EXTERNAL. From the broker log, it seems that Dispatch doesn't know EXTERNAL mechanism anymore: 2015-09-01 10:44:22 [Network] info Set TCP_NODELAY on connection to 172.23.39.11:53072 2015-09-01 1

C++ binding update - moving to master this week.

I have updated the C++ proton binding, for details see: http://people.apache.org/~aconway/proton/c-and-cpp.html http://people.apache.org/~aconway/proton The highlights of the change: - 0 overhead C++ facade classes, facade pointers point directly at C structs. - proton::counted_ptr for automated

Re: Qpid Dispatch Router 0.5 RC1

On Tue, 2015-09-01 at 10:50 +0200, Jakub Scholz wrote: > Hi Ted, > > I gave the RC1 a try and it seems that I'm now unable to connect to > the > qpidd broker using SASL EXTERNAL. From the broker log, it seems that > Dispatch doesn't know EXTERNAL mechanism anymore: I think this is PROTON-974. Wh

Re: windows 10 build - vs2015

On Sat, 2015-08-29 at 15:46 +, Ivan Judson wrote: > Hi, > > I'm continuing my investigation of building on w10 and vs15. I've > followed the instructions with cmake here: > > https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=blob_plai > n;f=INSTALL.md;hb=0.10 > > and at this point:

qpid 0.34 acl issues with auth=no

Hi, I've got a TravisCI job that runs a set of integration tests against qpid, and I'm using the newly uploaded qpidd 0.34 for ubuntu, from the `qpid/testing` PPA. I generally run the tests with auth disabled, using the following travis configuration: before_script: - sudo add-apt-repository ppa

SASL mechanism different between 0.9.1 and 0.10

Hi all,I noticed the following difference between 0.9.1 and 0.10 and I'm not able to use Qpid Proton C 0.10 for sending messages to Azure Service Bus (a queue for example).The endpoint is the same for both : amqps://:@.servicebus.windows.net/q1 I'm using the "send" example in the Proton solution

Re: Qpid Dispatch Router 0.5 RC1

Hi Andrew, I tried it with both master and the 0.10.x branch of Proton and it indeed seems to be fixed there. Thanks for pointing me to the JIRA. It is not that critical issue for me, so I don't think Robbie has to do 0.10.1 release just because of this. Thanks & Regards Jakub On Tue, Sep 1, 20

Re: windows 10 build - vs2015

Hey Andrew, Thanks for the reply, a couple of comments below (inline). On 9/1/15, 7:15 AM, "Andrew Stitcher" wrote: >On Sat, 2015-08-29 at 15:46 +, Ivan Judson wrote: >> Hi, >> >> I'm continuing my investigation of building on w10 and vs15. I've >> followed the instructions with cmake

Re: SASL mechanism different between 0.9.1 and 0.10

On Tue, 2015-09-01 at 14:32 +, Paolo Patierno wrote: > Hi all, > I noticed the following difference between 0.9.1 and 0.10 and I'm not > able to use Qpid Proton C 0.10 for sending messages to Azure Service > Bus (a queue for example). You don't say whether you are using Proton-C 0.10 on Window

RE: SASL mechanism different between 0.9.1 and 0.10

Hi, I wrote I'm under Windows 10 and Visual Studio 2015. I'm not using client authentication because as I said I'm executing the "send" application inside the Proton solution generated by cmake. The "send" application is very simple : It sends a simple Hello message without any other feature rel

[ANNOUNCE] Apache Qpid JMS 0.5.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid JMS 0.5.0. This is the fifth release of our new AMQP 1.0 JMS client, based around the Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS. The release is available now f

Re: qpid 0.34 acl issues with auth=no

On Tue, Sep 1, 2015 at 10:25 AM, Matt Broadstone wrote: > Hi, > I've got a TravisCI job that runs a set of integration tests against qpid, > and I'm using the newly uploaded qpidd 0.34 for ubuntu, from the > `qpid/testing` PPA. I generally run the tests with auth disabled, using the > following t

Re: SASL mechanism different between 0.9.1 and 0.10

Is there any chance you could use a mail application (or setting for this one) that respects the message-id of messages you reply to and adds a correct "references" header? Your messages keep on breaking up the threading of messages for me (and for many other people I'd wager). On Tue, 2015-09-01

Re: SASL mechanism different between 0.9.1 and 0.10

On 09/01/2015 07:29 PM, Andrew Stitcher wrote: You may have to modify the send example I suspect this is the send example using the messenger API. Is there a way to control the mechanisms used with that API? - To unsubscrib

RE: SASL mechanism different between 0.9.1 and 0.10

Yes Gordon ... You are right I'm speaking about messenger APIs Sent from my Windows Phone From: Gordon Sim Sent: ‎01/‎09/‎2015 20:39 To: users@qpid.apache.org Subject: Re: SASL mechanism different between 0.9.1