对卡在 CLOSE_WAIT 状态的连接进行故障排除 [英] Troubleshooting connections stuck in CLOSE_WAIT status

查看:45
本文介绍了对卡在 CLOSE_WAIT 状态的连接进行故障排除的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个在 Windows 上的 WebLogic 11g 中运行的 Java 应用程序,几天后,它变得没有响应.我注意到的一个可疑症状是,即使服务器处于空闲状态,netstat 中也会出现大量连接(大约 3000 个)并显示 CLOSE_WAIT 状态.由于应用程序服务器正在管理客户端连接,我不确定是什么原因造成的.我们还进行了许多回环到同一服务器的 Web 服务调用,但我相信这些连接会正确关闭.还有什么可能导致这种情况,如何解决这样的问题?

I have a Java application running in WebLogic 11g on Windows, which after several days, becomes unresponsive. One suspicious symptom I've noticed is that a large number of connections (about 3000) show up in netstat with a CLOSE_WAIT status even when the server is idle. Since the application server is managing the client connections, I'm not sure what's causing this. We also make a number of web service calls that loopback to the same server, but I believe those connections get closed properly. What else could cause this and how does one troubleshoot a problem like this?

推荐答案

问题是在 webLogic 中将Use JSSE SSL"设置为 true 触发的错误.使用 WebLogic 自己的 SSL 实现而不是 JSSE 对我们的应用程序来说不是问题,所以我只是取消选中该设置,问题就消失了.

The problem was a bug triggered by setting "Use JSSE SSL" to true in webLogic. Using WebLogic's own SSL implementation instead of JSSE is not a problem for our application, so I merely unchecked that setting and the problem disappeared.

这篇关于对卡在 CLOSE_WAIT 状态的连接进行故障排除的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆