+1 I tested the AMQP 0-10 client against Qpid C++ 0.34 & trunk and against MRG-M 3.0 & 3.2. I also spent some time playing with the broker.
On Wed, Feb 24, 2016 at 10:10 AM, Lorenz Quack <[email protected]> wrote: > > > On 22/02/16 11:51, Oleksandr Rudyy wrote: > >> Hi everyone, >> >> I created a new 6.0.1 RC3 build containing a fix for a blocker: >> >> QPID-6817 - [Java Broker] On abrupt connection close from client side when >> Broker is delivering messages to consumer, the delivering messages might >> not be released as part of close in some unlucky circumstances >> >> Please test and vote accordingly. >> >> The source and binary bundles are available from: >> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.1-rc3 >> >> Maven release artifacts including source and binary bundles are available >> from maven staging repo at: >> https://repository.apache.org/content/repositories/orgapacheqpid-1067 >> >> Kind regards, >> Alex >> >> Downloaded and verified checksums. > Ran some examples. > All looks good. > > +1 > > For next time: the checksum files do not contain the filenames they apply > to meaning you can't convenient use the checksum tools to verify the files. > Example: > $ sha1sum --check qpid-broker-6.0.1-bin.tar.gz.sha1 > sha1sum: qpid-broker-6.0.1-bin.tar.gz.sha1: no properly formatted SHA1 > checksum lines found > > Kind Regards, > Lorenz > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
