Hiram, I tried to get the stack trace (on unix its <Ctrl>\). I was not getting any useful information out of it. Basically there was nothing coming on trace when I was seeing my consumer hung.
I got curious about the stability of the SNAPSHOT releases, so when I ran the same consumer with AMQ 4.0.1 it was not hanging. But 9/25 SNAPSHOT release was hanging. Today I downloaded the latest SNAPSHOT 10/17 and tried it also it is hanging as well. But if I set the "activemq.prefetchSize" to 1 then only its hanging but if I remove the prefetchSize header property at the subscribe time, it doesn't hang and my while loop works and it pulls all the message from the queue. I don't understand why it's happening because if I run my consumer with AMQ-4.0.1 (old release) with "activemq.prefetchSize=1" my while loop works and it does not hang and my consumer pulls out all the messages from the queue. It seems like prefetchSize is only causing issue in the post 4.0.1 release (SNAPSHOT 9/25 and 10/17). Is it an expected behavior? I want to mention one important thing about my STOMP client implementation I have a connect and subscribe call and after that I have a while loop which is having "stomp_read" calls and ack's in it. Please let me know if you have any other question. Thanks! Vik -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram Chirino Sent: Monday, October 16, 2006 4:38 PM To: [email protected] Subject: Re: STOMP client hang problem with auto-ack Vik, Could you send us the broker side stack traces? I think it's like Ctrl-| on unix to get it to dump out the stacks. That should tell us if there is a hanging thread somewhere. On 10/16/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Any one noticed issue with STOMP client when consumer tries to auto-ack > a message. I am seeing this issue consistently. I have a STOMP producer > who is producing a message and a separate C program who is consuming > message using STOMP C. Both producer and consumer are running > concurrently, my consumer hangs after consuming 2 messages from the > queue. This behavior is consistent and every time consumer hangs after > consuming couple of messages. After that if I restart my consumer it > consumes 2 more messages and hangs again. > > > > If I try it with client side acknowledge it works fine. > > > > Any guidance will be helpful. > > > > Thanks! > > > > Vik > > > > > -- Regards, Hiram Blog: http://hiramchirino.com
