ApacheCon: Getting the word out internally

2016-07-18 Thread Melissa Warnkin
ApacheCon: Getting the word out internally Dear Apache Enthusiast, As you are no doubt already aware, we will be holding ApacheCon in Seville, Spain, the week of November 14th, 2016. The call for papers (CFP) for this event is now open, and will remain open until September 9th. The event is divid

proton-j Reactor: Best way to implement Concurrent Sender

2016-07-18 Thread Garlapati Sreeram Kumar
Hello All! We are using Proton-j Reactor framework & are trying to offer Send API in our EventHub Client offering to talk to Microsoft Azure Event Hubs (EventSender.Send(eventData)). To simplify the scenario lets say, we mapped each EventSender (in our client) to 1 Reactor – which maps to 1 Co

Re: Seeing a Qpid C++ master build failure in AppVeyor

2016-07-18 Thread Andrew Stitcher
On Fri, 2016-07-15 at 12:17 +0200, Justin Ross wrote: > Failed job: > https://ci.appveyor.com/project/ssorj/qpid-cpp/build/hammerandtong.2 > > AppVeyor config: > https://github.com/ssorj/qpid-cpp/blob/hammerandtong/etc/appveyor.yml > > Ths is a build-only version of the config I used for the reor

Re: qpid-proton 0.12.2 connection_engine and ssl

2016-07-18 Thread Cliff Jansen
Service bus authenticates to the link ("entity"), so it is perfectly normal to have connection and session operations succeed with bogus credentials followed by a link attach failure. However, I can't say that you actually have an authentication issue since you have success with at least one of th

Re: qpid-proton 0.12.2 connection_engine and ssl

2016-07-18 Thread Alan Conway
On Mon, 2016-07-18 at 02:03 -0700, Tobias Duckworth wrote: > OK, so I managed to fire up a local broker that requires SSL and > everything > works fine... I can open sessions, senders, receivers, send a message > etc. > > So it seems that the problem is specific to Azure, although not sure > why i

Re: qpid-dispatch link between brokers

2016-07-18 Thread Ganesh Murthy
Please take a look at the autoLink feature provided by the router (http://qpid.apache.org/releases/qpid-dispatch-master/book.html - section 2.5). You can create an "address" with prefix jms.queue and then setup two autoLinks in and out of the brokers. Create queues (jms.queue.first) in the broke

Re: qpid-proton 0.12.2 connection_engine and ssl

2016-07-18 Thread Tobias Duckworth
OK, so I managed to fire up a local broker that requires SSL and everything works fine... I can open sessions, senders, receivers, send a message etc. So it seems that the problem is specific to Azure, although not sure why it works with the non connection_engine build, but not with the connection