Jetty 8.1将日志文件泛洪为"Dispatched Failed".讯息 [英] Jetty 8.1 flooding the log file with "Dispatched Failed" messages

问题描述

我们将Jetty 8.1用作嵌入式HTTP服务器.在过载情况下，服务器有时会开始使用以下消息泛洪日志文件:

We are using Jetty 8.1 as an embedded HTTP server. Under overload conditions the server sometimes starts flooding the log file with these messages:

warn: java.util.concurrent.RejectedExecutionException
warn: Dispatched Failed! SCEP@76107610{l(...)<->r(...),d=false,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}...

同一条消息重复了数千次，并且日志记录的数量似乎使整个系统变慢.消息本身很好，我们的请求处理程序只是为了减慢及时处理请求的速度.但是大量的重复消息实际上使情况变得更糟，并使系统更难以从过载中恢复.

The same message is repeated thousands of times, and the amount of logging appears to slow down the whole system. The messages itself are fine, our request handler ist just to slow to process the requests in time. But the huge number of repeated messages makes things actually worse and makes it more difficult for the system to recover from the overload.

所以，我的问题是:这是正常的行为，还是我们做错了什么? 这是我们设置服务器的方式:

So, my question is: is this a normal behaviour, or are we doing something wrong? Here is how we set up the server:

Server server = new Server();
SelectChannelConnector connector = new SelectChannelConnector();
connector.setAcceptQueueSize( 10 );
server.setConnectors( new Connector[]{ connector } );
server.setThreadPool( new ExecutorThreadPool( 32, 32, 60, TimeUnit.SECONDS,
                                              new ArrayBlockingQueue<Runnable>( 10 )));

推荐答案

要看不到它，只需将命名为org.eclipse.jetty.io.nio.SelectChannelEndPoint的记录器设置为LEVEL = OFF.

To not see it, just set your named logger of org.eclipse.jetty.io.nio.SelectChannelEndPoint to LEVEL=OFF.

现在，为什么要看到它，这对于Jetty的开发人员来说更有趣.您能否详细说明您使用的是哪个特定版本的Jetty，以及您使用的是哪个特定的JVM?

Now as for why you see it, that is more interesting to the developers of Jetty. Can you detail what specific version of Jetty you are using and also what specific JVM you are using?

这篇关于Jetty 8.1将日志文件泛洪为"Dispatched Failed".讯息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！