Using non-blocking thread pool causes excessive RejectedExecutionExceptions to be logged ---------------------------------------------------------------------------------------- Key: JBWEB-276 URL: https://issues.jboss.org/browse/JBWEB-276 Project: JBoss Web Issue Type: Enhancement Security Level: Public(Everyone can see) Affects Versions: JBossWeb-7.2.0.Beta1 Reporter: James Livingston Assignee: Remy Maucherat Attachments: JBWEB-276-1.patch, JBWEB-276-2.patch When a finite-queue thread pool is used to process web requests, the queue being full can either block or drop the request. If you use a pool which drops requests, a RejectedExecutionException is thrown. Currently JIoEndpoint catches that exception the same as other ones such as being unable to create threads. When using a non-blocking pool, the task being rejected is not a critical error like other exceptions so should not be logged at ERROR level. Under excessive load, these exception will be continuously generated as requests are dropped, which cases a large amount of logging. Setting it to DEBUG level would stop that, but it would hide the potentially useful messages by default.