[
https://issues.apache.org/jira/browse/GUACAMOLE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835698#comment-17835698
]
Nick Couchman commented on GUACAMOLE-1939:
------------------------------------------
[~aylin]: The "CLOSED_WAIT" state is not something that Guacamole has any
control over. This is a function of the TCP stack in the underlying operating
system (Linux, in the case of Guacamole), and how long it leaves closed
sessions around before cleaning them up.
Also, in the future, if you have questions about Guacamole's behavior,
performance, etc., please post them to the mailing list, first rather than
opening Jira issues. After a discussion on the mailing list, if a bug or
required feature is identified you can proceed to open a Jira ticket, but it
would be better for these types of questions and discussions to be held on the
mailing list, first.
> After testing guacamole, the number of tcp link states in close_wait exceeds
> the number of established states
> -------------------------------------------------------------------------------------------------------------
>
> Key: GUACAMOLE-1939
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1939
> Project: Guacamole
> Issue Type: Bug
> Reporter: CaoShulin
> Priority: Major
> Attachments: 1.png
>
>
> Local host: Windows host
> Remote host: Windows host
> guacamole version: 1.5.4
> Protocol: rdp
> guacd：EulerOS 2.9 64bit | 4vCPUs | 8GiB
> Pressure test guacamole with jmeter. After the pressure test is stopped, the
> guacd server will have a close_wait tcp link state. Close_wait exceeds the
> number established. And the close_wait number will not be reduced, but will
> accumulate. See the attached picture.. Is the code not robust enough?
> !image-2024-04-10-17-56-47-729.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
