Carl Trieloff wrote:
Carl Trieloff wrote:
Robert Greig wrote:
On 18/09/2007, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
Has this been tested ?
Well we are running a continuous build so it does build and the tests
pass.
Of the three issues, QPID-531 was fixed by Martin (and includes
updated test case), QPID-573 has been fixed by Rafi and QPID-572 has a
fix for the most serious aspect (leaving a less critical ordering
issue QPID-601 when using selectors).
From the discussion on the other thread I think there is agreement we
can go ahead with M2 and work on the message ordering issue when using
selectors as a separate issue (to be scoped for M2.1 or later).
RG
I see our build server is currently showing failures on java-qpid-M2.
Give us a few to investigate as
I will base my vote from that.
Running org.apache.qpid.test.unit.topic.TopicSessionTest
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.351
sec <<< FAILURE!
Results :
... is the culprit.
Assuming that Martin's fix is in place on M2, then this may be the
QPID-601 race condition.
FWIW after looking at the code more, the impact of this race condition
is actually to strand certain messages inside the broker, not to deliver
them out of order.
--Rafael
