Re: activemq.prefetchSize behavior concerns in STOMP C client
Hey.. I just made some fixes recently to the stomp acking.. see: http://svn.apache.org/viewvc?view=revrevision=465990 This may fix it for ya. On 10/20/06, James Strachan [EMAIL PROTECTED] wrote: Some background on prefetch... http://incubator.apache.org/activemq/what-is-the-prefetch-limit-for.html Is the Stomp client either accurately specifying auto-ack mode or acknowledging the messages? Irrespective of the client used; if you don't acknowledge the messages in the prefetch buffer, the broker refuses to send more when the buffer is full until it receives acknowledgements. On 10/19/06, Dhawan, Vikram (LNG-DAY) [EMAIL PROTECTED] wrote: Hi, I am using STOMP C client with latest build available of AMQ (pre 4.0.2 10/17 build). I have some questions about how prefetchSize is affecting my client working. My STOMP C consumer is implemented in a way that once it connected to the AMQ server it loops and reads all the messages in the particular queue. And once all the messages are read it disconnects. What I am seeing here is if I have a prefetchSize value set then it only reads messages up to the prefetchSize value and then it blocks at the stomp_read call. If I don't have any prefetchSize value set then it loops and stomp_read reads all the messages in the queue. But my Openwire java client doesn't behave similarly. Even if I have a prefetchSize set to a small value in java client every nextMessage() call gives me a message if there is any message in the queue. I am not sure why there is different in prefetchSize working in STOMP and java client. Is this expected behavior? Any help would be appreciated. Thanks! Vik -- James --- http://radio.weblogs.com/0112098/ -- Regards, Hiram Blog: http://hiramchirino.com
RE: activemq.prefetchSize behavior concerns in STOMP C client
Hi Hiram, Thanks for the quick response and the fix. I am in process of testing it today and will let you know how it goes. James: thanks for describing the prefetch behavior for me. Vik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Friday, October 20, 2006 9:39 AM To: activemq-dev@geronimo.apache.org Subject: Re: activemq.prefetchSize behavior concerns in STOMP C client Hey.. I just made some fixes recently to the stomp acking.. see: http://svn.apache.org/viewvc?view=revrevision=465990 This may fix it for ya. On 10/20/06, James Strachan [EMAIL PROTECTED] wrote: Some background on prefetch... http://incubator.apache.org/activemq/what-is-the-prefetch-limit-for.html Is the Stomp client either accurately specifying auto-ack mode or acknowledging the messages? Irrespective of the client used; if you don't acknowledge the messages in the prefetch buffer, the broker refuses to send more when the buffer is full until it receives acknowledgements. On 10/19/06, Dhawan, Vikram (LNG-DAY) [EMAIL PROTECTED] wrote: Hi, I am using STOMP C client with latest build available of AMQ (pre 4.0.2 10/17 build). I have some questions about how prefetchSize is affecting my client working. My STOMP C consumer is implemented in a way that once it connected to the AMQ server it loops and reads all the messages in the particular queue. And once all the messages are read it disconnects. What I am seeing here is if I have a prefetchSize value set then it only reads messages up to the prefetchSize value and then it blocks at the stomp_read call. If I don't have any prefetchSize value set then it loops and stomp_read reads all the messages in the queue. But my Openwire java client doesn't behave similarly. Even if I have a prefetchSize set to a small value in java client every nextMessage() call gives me a message if there is any message in the queue. I am not sure why there is different in prefetchSize working in STOMP and java client. Is this expected behavior? Any help would be appreciated. Thanks! Vik -- James --- http://radio.weblogs.com/0112098/ -- Regards, Hiram Blog: http://hiramchirino.com
activemq.prefetchSize behavior concerns in STOMP C client
Hi, I am using STOMP C client with latest build available of AMQ (pre 4.0.2 10/17 build). I have some questions about how prefetchSize is affecting my client working. My STOMP C consumer is implemented in a way that once it connected to the AMQ server it loops and reads all the messages in the particular queue. And once all the messages are read it disconnects. What I am seeing here is if I have a prefetchSize value set then it only reads messages up to the prefetchSize value and then it blocks at the stomp_read call. If I don't have any prefetchSize value set then it loops and stomp_read reads all the messages in the queue. But my Openwire java client doesn't behave similarly. Even if I have a prefetchSize set to a small value in java client every nextMessage() call gives me a message if there is any message in the queue. I am not sure why there is different in prefetchSize working in STOMP and java client. Is this expected behavior? Any help would be appreciated. Thanks! Vik
