activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: DOS attack on activemq setup
Date Mon, 13 Apr 2015 16:01:12 GMT
that is a problem. The best we have at the moment is via

Having per adapter limits respected by the broker in the mkahadb case
would be a nice enhancement.

On 13 April 2015 at 15:10, xabhi <> wrote:
> 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:
> Sent from the ActiveMQ - User mailing list archive at

View raw message