简体繁体 English

FIN_WAIT Java监视应用程序问题

[英]FIN_WAIT Issue With Java Monitoring Application

原文 2011-10-13 17:29:21 1 1 java/ tcp

Having issues with FIN_WAIT1 on my RHEL 5.4 running Introscope. 在运行Introscope的RHEL 5.4上，FIN_WAIT1出现问题。 What I have observed so far is whenever the target JVM which we are monitoring using Introscope is hung the agent running on that host stop sending data and after some time the socket on the server (Introscope Server) goes in FIN_WAIT1 state and it remains there for a long time it gets cleaned up if we restart the target JVM. 到目前为止，我观察到的是，无论何时挂起我们正在使用Introscope监视的目标JVM时，在该主机上运行的代理都停止发送数据，并且一段时间后，服务器（Introscope Server）上的套接字进入FIN_WAIT1状态，并保持在那里。很长一段时间，如果我们重新启动目标JVM，它将被清除。

I would like to know if this is happening because of a bug in Introscope or is it something to do with TCP layer. 我想知道这是由于Introscope中的错误引起的还是与TCP层有关。

1 个解决方案

FIN_WAIT1 is at the TCP layer - it means your computer's tcp stack is waiting for one of the connection-close messages from the other side's TCP stack. FIN_WAIT1位于TCP层-这意味着您计算机的tcp堆栈正在等待来自另一端TCP堆栈的连接关闭消息之一。 It usually doesn't really cause much harm, other than taking some tiny amount of kernel state until it times out. 它通常不会真正造成太大的危害，除了在超时之前占用少量内核状态之外。 However sometimes it can prevent you from restarting a server on the same port, in which case you can set the SO_REUSESOCKET and/or SO_REUSEPORT options on the socket before opening it the first time. 但是，有时它可能会阻止您在同一端口上重新启动服务器，在这种情况下，可以在第一次打开套接字之前在套接字上设置SO_REUSESOCKET和/或SO_REUSEPORT选项。 (This does have some security implications if you're sharing the machine.) （如果共享机器，这确实会带来一些安全隐患。）