Hi Michael, thanks for these updates. Please provide details on any issues you experience (and raise appropriate Jira issues).
Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, Apr 17, 2009 at 6:46 PM, mjustin <michael.jus...@gmx.net> wrote: > > Update #2: > > Looks like it is only a problem in the Stomp Java client in ActiveMQ - I > will try to fix the source of my tests to see if it is a protocol error > (missing unsubscribe) or a problem in the underlying TCP transport layer. > > After some tweaking, my Delphi library shows and better results now - > depending on the steps at the end of the communication (unsubscribing, > disconnecting). > > Many thanks for your feedback, > and for bringing Hudson online :) > > Michael > > > mjustin wrote: > > > > Update: > > > > the test steps and results are: > > > > 1. send 20 messages to the broker, the admin console displays 20 > messages, > > numbered from 1 to 20 > > > > 2. consume 10 messages using Stomp client (5.3-Snapshot version) with > > "ack:auto", now the admin console displays only messages numbered from 13 > > to 20 - it looks like message 11 and 12 are lost > > > > 3. try to consume 10 messages again: the Stomp client only receives 8 > > messages > > > > I will try it with the current snapshot > > > > Best Regards, > > Michael Justin > > > > > > -- > View this message in context: > http://www.nabble.com/Stomp-ack%3Aauto-clears-all-remaining-messages-in-the-queue-tp23074533p23101402.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >