跳转到主内容

在 Web 服务代理 trace.log 中出现“无法刷新 HttpPCClient 中的缓冲区”错误

Views:
17
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

适用于

 

 E 系列 SANtricity Web 服务代理 3.2

问题

SANtricity Web Services 代理 trace.log 中的许多错误 "java.io.ioException :刷新 HttpPCClient 中的缓冲区失败。例如:

2020-05-05 21:39:06,216 ERROR [I/O dispatcher 87] d.a.r.HttpRpcClient [HttpRpcClient.java:225] [requestId=0, deviceId=N/A] Call for procedure id [674] failed
Caller+0 at devmgr.api.rpc.HttpRpcClient$1.failed(HttpRpcClient.java:225)
Caller+1 at org.apache. http.concurrent.BasicFuture.failed(BasicFuture.java:138)
Caller+2 at org.apache. http.impl.nio.client.DefaultClientExchangeHandlerImpl.executionFailed(DefaultClientExchangeHandlerImpl.java:101)
Caller+3 at org.apache. http.impl.nio.client.AbstractClientExchangeHandler.failed(AbstractClientExchangeHandler.java:426)
Caller+4 at org.apache. http.nio.protocol.HttpAsyncRequestExecutor.exception(HttpAsyncRequestExecutor.java:155)
java.io.IOException: Failed to flush the buffer in HttpRpcClient
 at devmgr.api.rpc.HttpRpcClient.flushBuffer(HttpRpcClient.java:508)
 at devmgr.api.rpc.HttpRpcClient.access$700(HttpRpcClient.java:57)
 at devmgr.api.rpc.HttpRpcClient$ContentEncoderOutputStream.flushBufferIfFull(HttpRpcClient.java:629)
 at devmgr.api.rpc.HttpRpcClient$ContentEncoderOutputStream.write(HttpRpcClient.java:619)
 at devmgr.api.rpc.StreamingChannel.sendMsg(StreamingChannel.java:104)
 at devmgr.api.rpc.HttpRpcClient$XdrMessageAsyncContentProducer.produceContent(HttpRpcClient.java:556)
 at org.apache. http.nio.protocol.BasicAsyncRequestProducer.produceContent(BasicAsyncRequestProducer.java:125)
 at org.apache. http.impl.nio.client.MainClientExec.produceContent(MainClientExec.java:262)
 at org.apache. http.impl.nio.client.DefaultClientExchangeHandlerImpl.produceContent(DefaultClientExchangeHandlerImpl.java:140)
 at org.apache. http.nio.protocol.HttpAsyncRequestExecutor.outputReady(HttpAsyncRequestExecutor.java:241)
 at org.apache. http.impl.nio.DefaultNHttpClientConnection.produceOutput(DefaultNHttpClientConnection.java:290)
 at org.apache. http.impl.nio.client.InternalIODispatch.onOutputReady(InternalIODispatch.java:86)
 at org.apache. http.impl.nio.client.InternalIODispatch.onOutputReady(InternalIODispatch.java:39)
 at org.apache. http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:152)
 at org.apache. http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:188)
 at org.apache. http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:341)
 at org.apache. http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
 at org.apache. http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
 at org.apache. http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
 at org.apache. http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
 at java.base/java.lang.Thread.run(Thread.java:834)
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.