I'll have to see if that trick works. We solved it by setting useAsyncSend = true. We also turned off the persistent data store (kahadb) because somehow we were getting a few messages caught in there that weren't being delivered. Maybe using the data store plus useCache=false would work. Its hard for us to duplicate the issue in testing as it seems we can't quite push enough data through it.
We probably should upgrade to v5.2, but there doesn't seem to be anything in the changelog that would indicate anything we need. Our sysadmin is quite conservative when it comes to certain things. Once v5.3 is released as stable, I'm going to try my best to get us upgrade to it. --Aaron rajdavies wrote: > > > On 4 Sep 2009, at 15:14, magellings wrote: > >> >> We too were having problems were number of pending of messages was a >> negative >> number and messages received was greater than number sent. We >> determined >> there were indeed duplicate messages being sent. >> >> We ended up setting useCache to false on the queue policy entry and >> the >> problem appears to be resolved. >> >> We too were sending a high volume of messages to our queues relatively >> quickly. >> -- >> View this message in context: >> http://www.nabble.com/Getting-negative-number-of-pending-messages-tp22106707p25295148.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > > It would be great to know if you still had the problem on the latest > 5.3 snapshot too > > cheers, > > Rob > > Rob Davies > I work here: http://fusesource.com > My Blog: http://rajdavies.blogspot.com/ > I'm writing this: http://www.manning.com/snyder/ > > > > > > -- View this message in context: http://www.nabble.com/Getting-negative-number-of-pending-messages-tp22106707p25298970.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
