Question

我在播放框架中执行了一些工作，但突然停止了，我使用了TRACE，最后我得到了这个=＆gt;

20:07:08,999 TRACE ~ connection already null in cleanup : no action
20:07:28,540 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:08:28,554 DEBUG ~ Closing Idle Channel [id: 0x01b140e8, /0.0.0.0:3699 => /190.144.216.75:80]
20:08:28,554 TRACE ~ 1 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:08:28,554 DEBUG ~ Channel Closed: [id: 0x01b140e8, /0.0.0.0:3699 :> /190.144.216.75:80] with attachment com.ning.http.client.providers.netty.NettyAsyncHttpProvider$DiscardEvent@272393
20:09:28,569 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:10:28,583 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:11:28,597 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:12:28,612 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:13:28,626 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:14:28,640 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).
20:15:28,655 TRACE ~ 0 idle channels closed (times: 1st-loop=0, 2nd-loop=0).

在日志中我没有得到任何Exception

Answer 1

我认为这是因为将日志级别转换为TRACE会导致记录每条信息。除此之外，IO总是很慢。这有时会暴露框架/服务器中的异常极端情况，因此您经常会看到不可预测的行为。

我建议仅针对选定的套餐将级别更改为TRACE。

服务器突然停止

1 个答案: