not really. with jdbc the number of connections can be a limitation. maybe try verify with kahadb to contrast.
getting a few broker thread dumps in quick succession would help identify where the broker is spending its time. On 2 October 2013 14:27, dhonorez <[email protected]> wrote: > We're using LevelDB. I'll post the config as soon as I get the chance. > > Are you, by any chance, thinking of this issue with LevelDB: > >> We've been using the levelDB store a month of two now in production on NFS >> (with standard file lock failover configured). We've had a corrupt store >> several times now in the last few weeks, with no errors in the logs... >> just queues piling up, and very low throughput. The only thing we could do >> to resolve this, is throw away the store, and start over. > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Slow-acknowledgement-tp4672049p4672143.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
