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
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
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
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
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
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
