On 10 August 2015 at 19:34, Robbie Gemmell robbie.gemm...@gmail.com wrote:
Hi all,
I have put up a second cut for 0.10, please test it and vote accordingly.
This fixes a crash (PROTON-976) reported against the previous spin,
and adds a known issue (PROTON-975) of possible failure using the
On 08/10/2015 02:34 PM, Robbie Gemmell wrote:
Hi all,
I have put up a second cut for 0.10, please test it and vote accordingly.
This fixes a crash (PROTON-976) reported against the previous spin,
and adds a known issue (PROTON-975) of possible failure using the
DIGEST-MD5 mechanism against
-1 unfortunately.
I've been testing against Dispatch and I'm seeing lots of timeouts on
the tests.
It turns out that pn_read_frame is used to parse text that is not a
frame header. It's actually the AMQP header so it interprets the string
AMQP as the frame length. Now that we're testing
I am cancelling the vote on the seconr RC for Proton 0.10, and will
shortly be preparing a third RC.
The changes in RC2 uncovered a issue, that while present previously
was not causing an observable problem before hand but now does
following the additional validation included in RC2 and this
Hi all,
I have put up a third cut for 0.10, please test it and vote accordingly.
Since RC2 there have been fixes for PROTON-978, PROTON-975, and PROTON-899.
The release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.10-rc3/
Maven artifacts
+1
Tested with dispatch router.
On Tue, 2015-08-11 at 21:08 +0100, Robbie Gemmell wrote:
Hi all,
I have put up a third cut for 0.10, please test it and vote
accordingly.
Since RC2 there have been fixes for PROTON-978, PROTON-975, and
PROTON-899.
The release archive and
+1
Built visual studio (2008, 2010, 2012, 2013)(x86, x64).
Ran tests against qpidd and activemq 5.12 brokers using qpid client auth.
- Original Message -
From: Robbie Gemmell robbie.gemm...@gmail.com
To: users@qpid.apache.org, pro...@qpid.apache.org
Sent: Tuesday, August 11, 2015
