Netty connector hang up after repeated buffer overflow errors when writing data #5753

[jbescos]

#5753

I didn't include a test because it is tricky. I was testing it with the example provided in the issue.

[jbescos]

It looks the continuous integration was aborted, I am going to kick the build again:

[INFO] Running org.glassfish.jersey.tests.e2e.client.connector.proxy.ProxyTest$HttpUrlConnectorProviderProxyTest
script returned exit code 143
Sending interrupt signal to process
[Pipeline] // node
[Pipeline] }
[Pipeline] }
[Pipeline] // stage
[Pipeline] // withEnv
[Pipeline] }
Failed in branch JDK 21
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch JDK 11
script returned exit code 143
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Failed in branch JDK 8
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] End of Pipeline
org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: c5ef47a2-ce42-451d-9468-9dab15aa5346

GitHub has been notified of this commit’s build result

Finished: ABORTED

[senivam]

I've aborted it on purpose. Once it was already built. Today it was started again due to the re-indexing. And there is an issue with executors on the JIPP, so I was reducing load on executors.