+1
* tested the stand-alone console
On Tue, Nov 14, 2017 at 9:01 AM, Ted Ross wrote:
> Please cast your vote on this thread to release RC3 as the official Qpid
> Dispatch Router version 1.0.0.
>
> Qpid Dispatch Router 1.0.0 RC3 can be found here:
>
> https://dist.apache.org/repos/dist/dev/q
+1
* verified signature and checksums
* passes self test
* ran various multi-router tests
* passes qpid-interop-test types test with ProtonC, ProtonPython, and
AmqpNetLite shims
* passes qpid-interop-test large_content test with AmqpNetLite shim
- Original Message -
> From: "Ted Ross"
>
On 16/11/17 15:05, Ken Giusti wrote:
Hi Andreas,
100% totally untested, but...
The Container.connect() method takes an SSLDomain object via the
ssl_domain parameter. You'll want to instantiate the
proton.SSLDomain, calling set_credentials to setup the CA to use to
validate the broker's cert.
On 16/11/17 17:30, James Sears wrote:
Is there a way - using the python proton reactor API - to do what I'd call
dynamic message selection?
By this I mean I'd like my application to do something like this:
1. receive message M1 on queue Q1 with unique correlation_id N.
2. send message M2 to to
Is there a way - using the python proton reactor API - to do what I'd call
dynamic message selection?
By this I mean I'd like my application to do something like this:
1. receive message M1 on queue Q1 with unique correlation_id N.
2. send message M2 to topic T1 with correlation_id N and reply_t
+1 ... I built it from source and run some of my tests with different AMQP
1.0 clients as well as against the Qpid C++ broker.
Jakub
On Tue, Nov 14, 2017 at 2:01 PM, Ted Ross wrote:
> Please cast your vote on this thread to release RC3 as the official Qpid
> Dispatch Router version 1.0.0.
>
> Q
Hi Andreas,
100% totally untested, but...
The Container.connect() method takes an SSLDomain object via the
ssl_domain parameter. You'll want to instantiate the
proton.SSLDomain, calling set_credentials to setup the CA to use to
validate the broker's cert.
connect() also takes a URL, the scheme
+1
I performed the following tests:
* built successfully client from source distribution bundle
* ran successfully Hello, Spout and Drain examples against Qpid
Broker-J built from master
* ran successfully Qpid Broker-J system tests (on master) using 6.3.0
staging artefacts
* verified checksums an
+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.
Jakub
On Wed, Nov 15, 2017 at 4:59 PM, Oleksandr Rudyy wrote:
> Hi all,
>
> I built a candidate release for version 6.3.0 of Qpid JMS AMQP 0-x.
>
> Please test and vote accordingly.
>
> The source and
+1
My testing:
* check all checksums on source and binary bundles
* run apache-rat:check
* build and run all tests of the source bundle
* run Spout/Drain example against Qpid Broker-J (git master)
On Wed, Nov 15, 2017 at 4:59 PM, Oleksandr Rudyy wrote:
> Hi all,
>
> I built a candidate re
Hello All,
I need to use a Python3 AMQP 1.0 API in order to access a Qpid C++ Broker.
So I am going for the Proton API since the Qpid Python API is only usable
with Python 2.
In the past I used the C++ Qpid API with SSL and it worked fine. There you
just had to set three environment variables and
On 15 November 2017 at 14:13, Gordon Sim wrote:
> On 10/11/17 18:11, Keith W wrote:
>>
>> I infer that CPP Broker must be optimistically sending the
>> Disposition back to the client before the data is sync'd, so that is
>> why you see better performance (but with a lesser guarantee).
>
>
> I don'
Indeed, welcome!
On 16 November 2017 at 07:57, Lorenz Quack wrote:
> Welcome Chris,
>
> Good to have you on the team!
>
> On Wed, Nov 15, 2017 at 7:02 PM, Adel Boutros wrote:
>
>> Welcome Chris!!
>>
>> From: Chris Richardson
>> Sent: Wednesday, November 15, 2017
13 matches
Mail list logo
