Yeah, good idea. I've made this change. On Tue, Nov 15, 2011 at 11:43 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> On Tue, Nov 15, 2011 at 4:08 PM, Jon Anstey <jans...@gmail.com> wrote: > > FYI took another look at this and it is not a real issue. When using > async > > sends in ActiveMQ on the producer side we can't really guarantee the > order > > in which messages will be added to the queue. To gaurantee order we can > > either enable sync sends, persistent messages, or transactions (all boil > > down to sync sends...). I made a fix for the test here: > > http://svn.apache.org/viewvc?view=revision&revision=1202227 > > > > Great. I wonder if we should just add logic to the BaseJmsTest class > (or watever its called) to enable sync send by default? > > > > Cheers, > > Jon > > > > On Mon, Nov 14, 2011 at 8:21 AM, Jon Anstey <jans...@gmail.com> wrote: > > > >> Was looking into this on Friday but didn't solve it. I'll have another > >> look today but if someone is really interesting in digging in ActiveMQ > ;) > >> the hint is that it works when you disable async sends. > >> > >> > >> On Sun, Nov 13, 2011 at 6:46 AM, Jean-Baptiste Onofré <j...@nanthrax.net > >wrote: > >> > >>> Hi Christian, > >>> > >>> I guess it depends of the JMS connection pool configuration (and the > >>> message retention/timeout). > >>> > >>> I will try to take a look later today from the airport. > >>> > >>> Regards > >>> JB > >>> > >>> > >>> On 11/13/2011 12:36 AM, Christian Müller wrote: > >>> > >>>> I'm a bit surprising about this failed unit test [1]. It looks like on > >>>> slow > >>>> boxes like the Jenkins server and Jon's Laptop ( sorry for that ;-) ) > the > >>>> messages arrived out of order or we loose one. Is this (a known) > issue in > >>>> ActiveMQ? Because this test run very well on my machine, I cannot dig > >>>> deeper in this issue... > >>>> > >>>> [1] > >>>> https://builds.apache.org/job/**Camel.trunk.fulltest/553/org.** > >>>> > apache.camel$camel-jms/**testReport/org.apache.camel.**component.jms/** > >>>> JmsSelectorInTest/**testJmsSelectorIn/< > https://builds.apache.org/job/Camel.trunk.fulltest/553/org.apache.camel$camel-jms/testReport/org.apache.camel.component.jms/JmsSelectorInTest/testJmsSelectorIn/ > > > >>>> > >>>> Best, > >>>> Christian > >>>> > >>>> > >>> -- > >>> Jean-Baptiste Onofré > >>> jbono...@apache.org > >>> http://blog.nanthrax.net > >>> Talend - http://www.talend.com > >>> > >> > >> > >> > >> -- > >> Cheers, > >> Jon > >> --------------- > >> FuseSource > >> Email: j...@fusesource.com > >> Web: fusesource.com > >> Twitter: jon_anstey > >> Blog: http://janstey.blogspot.com > >> Author of Camel in Action: http://manning.com/ibsen > >> > >> > > > > > > -- > > Cheers, > > Jon > > --------------- > > FuseSource > > Email: j...@fusesource.com > > Web: fusesource.com > > Twitter: jon_anstey > > Blog: http://janstey.blogspot.com > > Author of Camel in Action: http://manning.com/ibsen > > > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ > -- Cheers, Jon --------------- FuseSource Email: j...@fusesource.com Web: fusesource.com Twitter: jon_anstey Blog: http://janstey.blogspot.com Author of Camel in Action: http://manning.com/ibsen
