PUSH-000183:处理程序在缓冲区中未留下任何空间

Question

我在服务器日志中不断看到以下警告和堆栈跟踪，想知道出了什么问题以及如何解决它。我检查了名称 PUSH-000183，但它只显示"消息通道上发生通信错误"。

2016-04-20 13:37:42.452|WARN|Diffusion: InboundThreadPool Thread_1|PUSH-000183|Message channel error: 'NIOBufferedChannel@571714020[connected local=/10.96.130.21:8070 remote=/10.96.1.36:24832] : Closed(UNEXPECTED_ERROR) ServerInboundTask@542477fd HTTPConnectionHandler@2641ae33[partial request - more expected]: handler left no space in buffer ' caused by 'ServerInboundTask@542477fd HTTPConnectionHandler@2641ae33[partial request - more expected]: handler left no space in buffer'.|com.pushtechnology.diffusion.io.message.MessageChannelException
com.pushtechnology.diffusion.io.message.MessageChannelException: ServerInboundTask@542477fd HTTPConnectionHandler@2641ae33[partial request - more expected]: handler left no space in buffer
at com.pushtechnology.diffusion.io.nio.NIOBufferedChannel.logClosingException(NIOBufferedChannel.java:647)
at com.pushtechnology.diffusion.io.nio.NIOBufferedChannel.logAndClose(NIOBufferedChannel.java:613)
at com.pushtechnology.diffusion.io.nio.AbstractReadSelector$InboundTask.close(AbstractReadSelector.java:410)
at com.pushtechnology.diffusion.io.nio.AbstractReadSelector$InboundTask.run(AbstractReadSelector.java:351)
at com.pushtechnology.diffusion.threads.FastThreadPool$PoolWorker.run(FastThreadPool.java:783)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalStateException: ServerInboundTask@542477fd HTTPConnectionHandler@2641ae33[partial request - more expected]: handler left no space in buffer
at com.pushtechnology.diffusion.io.nio.AbstractReadSelector$InboundTask.run(AbstractReadSelector.java:324)

这是否仅限于使用 XHR 连接的客户端，或者 websocket 也会受到影响？

Answer 1

当客户端向更大的服务器发送消息时，会发生这种情况比连接器.xml中配置的输入缓冲区大小。

它将断开客户端的连接，如果已配置，则可能会重新连接这样做。无论传输如何，任何客户端都可能发生这种情况（XHR，Websockets等）。

您需要增加连接器中的输入缓冲区大小.xml匹配您期望的最大消息。例如，如果你是发送最大 256K 的消息，您可以使用以下内容配置：

<socket-conditioning>
     <!-- If this value is less than max-message-size defined in 
          Server.xml, it will be
          overwritten by the latter. -->
     <input-buffer-size>256k</input-buffer-size>
     <!-- Other config... -->
</socket-conditioning>