I just thought of another case where broker can be crashed. This is a case where a rogue app sends copious amount of persistent messages with no consumer and causes disk space to fill up making the broker unavailable.
I am using multiKahaDB in my setup and have grouped it based on destination patterns (a logical grouping of related destinations). But the kind of scenario I have described can be prevented from affecting other applications If I can put size limit on each of multiKahaDB persistent adapter separately otherwise one multiKahaDB can use entire remaining space for itself. That way broker won't run out of space for all destinations but only a group of destinations thus preventing the crash of entire setup. Is there any KahaDB configuration already present which will help in this case? Thanks, Abhi -- View this message in context: http://activemq.2283324.n4.nabble.com/DOS-attack-on-activemq-setup-tp4694598p4694820.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
