thinking a bit more, the simplest explanation is that you are reaching your memory usage limits and pending messages are no longer cached in memory. As a result, dispatch now needs to read from the store which will be slower. Do you notice an increase in queue depth before the slowdown?
post your xml configuration, that will help diagnose. On 3 August 2011 09:09, James Black <be_st...@yahoo.co.uk> wrote: > Hi, > > no there are no slow advisory messages in the logs. We used to receive > these when using the topic and it would block our producers that added to > the topic, but we have not seen this since we changed to a virtual topic. > > I'll try and arrange to capture some stack traces, the help is appreciated > :> > > Thanks, > > Justin > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-JDBC-Storage-Slow-down-tp3712166p3714722.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://fusesource.com http://blog.garytully.com
