[ https://issues.jboss.org/browse/JBWEB-276?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-276: ----------------------------------------------- James Livingston <jlivings(a)redhat.com&gt; made a comment on [bug 985191|https://bugzilla.redhat.com/show_bug.cgi?id=985191] For the default blocking thread pools, a RejectedExecutionException means a serious problem occurred, yes. If you switch the web container over to using a non-blocking thread pool however, so that it drops requests rather than blocking, it is expected that you would receive these. Currently if you want to make JBoss drop web requests when there are too many, it writes a large number of these errors out into the log, which would have performance implications reducing the usefulness of dropping request under excessive load. If you don't want to hide the message since it is serious for blocking thread pools, is there an alternative which would let people using non-blocking thread pools hide it? It would be possible to move it to a different logging category, which could be turned off, but adding a new logging category for one message seems excessive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira