WSO2 EI 6.6.0 连接超时间歇性问题

Question

我们在 WSO2 EI 中观察到一个非常奇怪的行为，即 WSO2 服务器停止发送 HTTP 请求，尽管 WSO2 中的所有内容都继续正常工作。

我们观察如下日志。

WARN {org.apache.synapse.transport.passthru.TargetHandler} - Connection time out after while in state : REQUEST_DONE Socket Timeout : 600000 correlation_id : null Remote Address : localhost/127.0.0.1:8243
TID: [-1234] [2022-03-09 09:14:42,439]  WARN {org.apache.synapse.FaultHandler} - ERROR_CODE : 101507
TID: [-1234] [2022-03-09 09:14:42,439]  WARN {org.apache.synapse.FaultHandler} - ERROR_MESSAGE : Error in Sender
TID: [-1234] [2022-03-09 09:14:42,439]  WARN {org.apache.synapse.FaultHandler} - ERROR_DETAIL : Error in Sender
TID: [-1234] [2022-03-09 09:14:42,439]  WARN {org.apache.synapse.FaultHandler} - ERROR_EXCEPTION : null
TID: [-1234] [2022-03-09 09:14:42,439]  WARN {org.apache.synapse.FaultHandler} - FaultHandler : Endpoint [wso2-delay-url]
TID: [-1234] [2022-03-09 09:14:42,440]  WARN {org.apache.synapse.FaultHandler} - FaultHandler executing impl: org.apache.synapse.mediators.MediatorFaultHandler
TID: [-1234] [2022-03-09 09:14:42,440]  WARN {org.apache.synapse.mediators.MediatorFaultHandler} - Executing fault handler mediator : org.apache.synapse.mediators.base.SequenceMediator
TID: [-1] [2022-03-09 09:14:42,443]  WARN {org.apache.synapse.transport.passthru.SourceHandler} - Connection time out after request is read: http-incoming-250 Socket Timeout : 600000 Remote Address : /127.0.0.1:60144

因此，尽管它尝试连接的应用程序运行良好，但连接超时开始发生。

日志中的其他一些观察结果如下：

TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_5701187744473942267.dat
TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_5286863810950226078.dat
TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_15656718439953223175.dat
TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_6161525619097223194.dat
TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_16101322891943797477.dat
TID: [-1] [2022-03-09 11:55:22,668]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_5181555544199697780.dat
TID: [-1] [2022-03-09 11:55:22,669]  WARN {org.apache.axiom.util.blob.OverflowBlob} - Cleaning up unreleased temporary file /opt/<organisationName>/applications/wso2ei-6.6.0/wso2/tmp/tmp_7115647804012046335.dat
TID: [-1] [2022-03-09 11:55:23,005]  WARN {org.apache.synapse.FaultHandler} - FaultHandler executing impl: org.apache.synapse.endpoints.AddressEndpoint
TID: [-1] [2022-03-09 11:55:23,006]  WARN {org.apache.synapse.FaultHandler} - FaultHandler executing impl: org.apache.synapse.mediators.MediatorFaultHandler
TID: [-1] [2022-03-09 11:55:23,006]  WARN {org.apache.synapse.mediators.MediatorFaultHandler} - Executing fault handler mediator : org.apache.synapse.mediators.base.SequenceMediator
TID: [-1] [2022-03-09 11:55:23,006]  WARN {org.apache.synapse.FaultHandler} - FaultHandler executing impl: org.apache.synapse.endpoints.AddressEndpoint
TID: [-1] [2022-03-09 11:55:23,007]  WARN {org.apache.synapse.FaultHandler} - FaultHandler executing impl: org.apache.synapse.mediators.MediatorFaultHandler
TID: [-1] [2022-03-09 11:55:23,007]  WARN {org.apache.synapse.mediators.MediatorFaultHandler} - Executing fault handler mediator : wso2-service-admin-change-service-state

TID: [-1] [2022-03-09 12:03:35,668]  WARN {org.apache.synapse.core.axis2.SynapseCallbackReceiver} - Synapse received a response for the request with message Id : urn:uuid:0b0cf1bb-b88a-4ce9-b5fe-c132a05dd29c and correlation_id : null But a callback is not registered (anymore) to process this response

毕竟存在错误，最后我在 WSO2 EI 服务器的 http_access 和审核日志中没有看到任何日志，但我可以看到 WSO2Carbon 日志仍然存在，用于 WSO2 中的其他处理。

服务器重新启动后一切开始正常工作。

现在，我们已在 25 天的间隔内观察到这种行为两次。

有人知道为什么会发生这种情况吗？

如果需要更多详细信息，请告诉我。谢谢！