Thanks for testing Gard, We will backport that implementation used in 4.1 to next 4.0.2 version as soon as it gets a little more testing.
On 7/4/06, gard <[EMAIL PROTECTED]> wrote:
Hi, I just tried the 4.1 snapshot and it seems like it is fixed in that version. I am now not experiencing the same problem with the message not beeing dequeued. thx for your help. regards, gard James.Strachan wrote: > > BTW I wonder if you could give version 4.1-SNAPSHOT a quick try to see > if that resolves your issue? Hiram refactored the code the other day > to make its flow control better, there's a chance this issue might be > fixed. > > On 7/4/06, gard <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> i added some debug statements in the stomp.rb file and this is what >> ActiveMessaging are sending: >> >> => Subscribing to /queue/Catchall Service (processed by >> CatchallServiceProcessor) >> SUBSCRIBE >> destination:/queue/Catchall Service >> content-length: 0 >> content-type: text/plain; charset=UTF-8 >> >> When I used the Stomp client class directly without ActiveMessaging this >> was >> my header when i set ack to Auto: >> >> SUBSCRIBE >> destination:/queue/Catchall Service >> ack:auto >> content-length: 0 >> content-type: text/plain; charset=UTF-8 >> >> So it seems to me that ActiveMessaging does not specify the >> acknowledgement >> mode and it shoudl be auto-ack. >> >> 1 note is that when i use the Stomp client directly and i set auto in the >> headers i still need to do do >> c.acknowledge(msg) for the message to be removed from the queue. It seems >> this is not the desired behaviour right? >> >> gard >> >> > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Stomp-and-ActiveMessaging-does-not-remove-messages-from-Queue-tf1889402.html#a5167468 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
