Yes, it was a case of not acking the message + ignorance of the stomp protocol.
Here is the rest of the story: http://www.nabble.com/forum/ViewPost.jtp? post=5595219&framed=y btw, using my perl client, I subscribed with a explicit, ack:auto, header and it worked too (against AMQ 4.0.1). - Sandeep On Tue, 2006-08-01 at 11:09 -0400, Hiram Chirino wrote: > you should test against either 4.1-SNAPSHOT or a 4.0.2 SNAPSHOT. Some > fixes were done that affect the aking of message in STOMP. > > On 7/31/06, Sandeep Chayapathi <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I just started using ActiveMQ4.0.1. To begin with, Im using the STOMP > > protocol, via the perl client. > > > > I have a test script (write.pl) that generates 10 messages, @ 1 message > > per second (destination: /queue/FOO.test). Another script (read.pl), > > tries to read these messages from ActiveMQ, in a while(1) loop. > > > > What I found was that the read.pl would get every 2nd message! > > > > Also, using the "browse" script, provided by activemq, I found that the > > destination contained all the 10 messages. Subsequent runs of read.pl do > > not pull any messages at all. Any help to sort this out is appreciated. > > Thanks. > > > > - Sandeep > > > > > >
