We have been encountering similar problems, but no definitive reproducible steps. Our analysis is pointing towards having the persistent flag turned on for messages. If the messages are flagged as persistent, then we can encounter non-responsive consumers. Understand that the consumer is not the problem, it seems to be more with the broker. The broker stops sending messages to a consumer that is able to consume -- it is not a "slow consumer" situation. If the messages are flagged as non-persistent, then everything works fine. We are still working on narrowing down the problem. You may want to check your message settings to see if you are using persistence or not.
On Tue, Jan 27, 2009 at 11:44 AM, Gabe Westmaas <gabe.westm...@mailtrust.com > wrote: > Hey all, > > One of the developers in our company is writing an application that uses > NMS and every once in a while the queue becomes unresponsive to consumers, > although producers can continue to produce to it. Other times a message > will get stuck at the top of the queue and producers and consumers will read > and write past it. > > After talking with him, he is using it a little strangely, and I was just > wondering if anyone can confirm this might cause the problem, since we can't > always recreate the problem reliably and thus know if we have fixed it. > > His NMS consumer had a prefetch of 1000, but after reading a maximum of 50 > messages, he disconnects and reconnects. It seems like this shouldn't cause > an issue, especially since there is only one consumer. > > After changing the prefetch to 20, we couldn't recreate the problem at all, > but even now, after setting it back to 1000 we still can't recreate the > issue again. > > Any suggestions or ideas? > > Thanks! > Gabe > >
