Rafi. do you have a test case that can reproduce the problem in 602? I've been trying to do so by populating the queue and then connect a client wils sending more messages. So far it always gets the messages in the right order. I haven't had much time to get a failing test so i can test my solution so he you have such a test that would really help.
Martin, The north end of Skye. Near the mobile mast. On 15/09/2007, Rafael Schloming <[EMAIL PROTECTED]> wrote: > Robert Greig wrote: > > On 14/09/2007, Rafael Schloming <[EMAIL PROTECTED]> wrote: > > > >> This is a tricky issue. There are actually two bugs here. The correct > >> fix for QPID-572 (the original patch submitted to the JIRA) actually > >> causes another race condition to be more likely. I've described the > >> other race condition in detail in QPID-601. > > > > Ah ok. It is useful to split this into the real issues. > > > >> So basically if we want to release M2 in a timely manner we need to > >> choose between selectors with correct message ordering and a higher > >> chance of messages being stranded, or selectors with incorrect message > >> ordering and a lower chance of messages being stranded. > > > > OK my own view is that stranded messages are worse than out of order > > messages therefore I would say we go for selectors with incorrect > > message ordering and a lower chance of messages being stranded. > > > > But we should note in the release notes that when using selectors > > ordering guarantees are "relaxed". > > > > What do others think? > > I agree that's the best option if there is no simple fix for QPID-601. > > --Rafael > > -- Martin Ritchie
