On 27 February 2018 at 14:57, Oleksandr Rudyy wrote:
> Hi all,
>
> I built a release candidate for a Qpid Broker-J 7.0.2.
> Please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.2-rc1
>
> T
I raised QPID-8113 for this issue and pushed a simple fix.
I'll raise a separate JIRA covering the fact that the error handling here
is poor, an unknown filter should really cause an attach{source: null},
followed by an immediate detach rather than closing the connection - and
certainly not a deco
On 28/02/18 13:20, Rob Godfrey wrote:
I would assume this is not a new error
Agreed, was noting in passing.
... from the looks of things this is
the Broker not supporting the "apache.org:selector-filter:string" filter
type, and choking on the fact in a less than graceful way.
Looking at the B
On 28 February 2018 at 12:17, Gordon Sim wrote:
> On 27/02/18 14:57, Oleksandr Rudyy wrote:
>
>> Hi all,
>>
>> I built a release candidate for a Qpid Broker-J 7.0.2.
>> Please give it a test out and vote accordingly.
>>
>
> +1
>
> Verified hashes and signatures, built from source including tests,
On 27/02/18 14:57, Oleksandr Rudyy wrote:
Hi all,
I built a release candidate for a Qpid Broker-J 7.0.2.
Please give it a test out and vote accordingly.
+1
Verified hashes and signatures, built from source including tests, ran
python examples against it, ran qpid::messaging against it, ran s
+1
built for source and ran java-mms tests for 0-9-1 and 1.0
started broker and kicked tires using management console
sent / received messages using JMS & Python (AMQP 1.0)
On 28 February 2018 at 11:39, Oleksandr Rudyy wrote:
> +1
>
> I performed the following testing:
>
> * built from source b
+1
I performed the following testing:
* built from source bundle and ran tests using java-mms.10 profile
* verified signatures and checksums
* started broker
* using web management console
** added test queue
** added node auto-creation policy
** created queue query and exported the results in C
+1.
My testing was:
1) Verified the md5/sha checksums on all distribution artefacts
2) Verified signatures on all the distribution artefacts
3) Ran apache RAT
4) Built/ran test profile mms/bdb 0-9/1.0 from source bundle (Qpid JMS
Client 0.26.0/0.29.0)
5) Generally kicked the tyres within the Web
