简体   繁体   English

WSO2 EI - 6.6.0 https 请求 CLOSE_WAIT

[英]WSO2 EI - 6.6.0 https request CLOSE_WAIT

I have a problem with wso2 EI 6.6.0.我对 wso2 EI 6.6.0 有疑问。 I send a https request to wso2 (soap proxy services) with a connection:close header.我通过连接向 wso2(soap 代理服务)发送 https 请求:关闭 header。 calls the endpoint and returns a response to the client.调用端点并向客户端返回响应。 problem is - the connection remains in the close_wait state on the server (linux) (telnet | grep CLOSE_WAIT) and with each new call, the number of connections in the close_wait state will increase.问题是 - 连接保留在服务器(linux)上的 close_wait state 中(telnet | grep CLOSE_WAIT),并且每次新调用时,close_wait Z9ED39E2EA9314586B6EZ9857A 中的连接数将增加。

only solution is add this parameters to service.唯一的解决方案是将此参数添加到服务中。

<header action="remove" name="connection:close" scope="transport"/>
     <header action="remove" name="connection" scope="transport"/>
     <property action="remove" name="connection" scope="axis2"/>

but it's not perfect because I must to modify all the services.但这并不完美,因为我必须修改所有服务。 is there a solution how to set this at the wso2 level?有没有解决方案如何在 wso2 级别进行设置? is this a bug in wso2 or axis?这是 wso2 或轴中的错误吗?

thanks谢谢

I'm not really sure how the Connection: Close header is causing this issue and how removing it from synapse runtime resolves it.我不太确定Connection: Close header 是如何导致此问题的,以及如何从突触运行时中删除它来解决它。

But to answer your question, to intercept requests coming into WSO2 EI you can write a custom synapse handler .但要回答您的问题,要拦截进入 WSO2 EI 的请求,您可以编写自定义突触处理程序 You can then engage it per service or globally.然后,您可以按服务或全局使用它。

On a side note have a look at HTTP tuning parameters as well, https://docs.wso2.com/display/EI660/Tuning+the+HTTP+Transport附带说明一下 HTTP 调整参数以及https://docs.wso2.com/display/EI660/Tuning+the+HTTP

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM