Update remoting to 2.62.2 in stable-2.19.x #2618
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR picks the latest available version of remoting stable-2.x. All the fixes have been integrated into remoting-3.0 and soaked enough.
Stability: Turn on SO_KEEPALIVE by default and provide CLI option to turn it off again.
([FIXED JENKINS-38539] Turn on SO_KEEPALIVE and provide CLI option to turn it off again remoting#110)
Prevent
NullPointerException
inEngine#connect()
when host or port parameters arenull
or empty.([FIXED JENKINS-37539] - Prevent NPE in Engine#connect() when host or port are null or empty remoting#101)
Fix resource leak in
remoting.jnlp.Main
.([CID-152201] - Fix resource leak in remoting.jnlp.Main remoting#102)
Resource leak in Encryption Cipher I/O streams on exceptional paths.
([CID-152200,CID-152202] - Resource leak in Cipher I/O streams on exceptional paths remoting#104)
@olivergondza @reviewbybees