Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages may be lost when the server proactively closes the socket. #82

Open
ph228228 opened this issue Dec 26, 2022 · 0 comments
Open
Labels

Comments

@ph228228
Copy link

Jenkins and plugins versions report

Environment
Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

centos7

Reproduction steps

When the server proactively closes the socket, the client does not detect the EOF and fails to close the socket. When the next syslog message is sent, the application layer does not throw an exception. As a result, the client considers that the message has been sent successfully, but the server does not process the message.

Expected Results

The client can identify that the server proactively closes the socket.

Actual Results

but not

Anything else?

No response

@ph228228 ph228228 added the bug label Dec 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant