Dear team, I am facing an issue on a process exploiting the AbortConsumerStrategy, ie disconnection from time to time. I cannot reproduce the case as it only happens in Production environment but I suspect the Strategy applies here. I have monitored the process for an hour an was able to see that around 27k events were pushed to the pool of concerned process. As it is quite a volume, what would be the appropriate properties to use? We have increased the memorylimit from 400MB to 2000MB and increased the maxSlowduration from 15k to 90k but still face the issue. Do you see a link? I am using activemq 5.5.1.
Thanks a lot for your enlightenment. Francis -- View this message in context: http://activemq.2283324.n4.nabble.com/AbortSlowConsumerStrategy-Recommendation-Advices-tp4678543.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
