-
Bug
-
Resolution: Fixed
-
Major
-
-
2.387
If a controller sends a ping and the agent does not respond, the computer is disconnected as expected. But if the agent sends a ping and the controller does not respond, a message is logged by the agent noting the failure but the connection is not closed.
- is caused by
-
JENKINS-35190 Improper PingThread handling
-
- Resolved
-
-
JENKINS-46680 Computer offline by ping thread leaves the channel half open
-
- Resolved
-
- relates to
-
JENKINS-25695 Make it easy to distinguish master-side ping failure and slave-side ping failure
-
- Open
-
- links to
[JENKINS-70414] Ping thread failures on agent side were ignored
Link |
New:
This issue is caused by |
Link |
New:
This issue is caused by |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "jenkins #7580 (Web Link)" [ 28439 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Link | New: This issue relates to JENKINS-25695 [ JENKINS-25695 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |
Released As | New: 2.387 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |
Labels | Original: agents lts-candidate remoting robustness | New: 2.375.3-fixed agents remoting robustness |
Labels | Original: 2.375.3-fixed agents remoting robustness | New: 2.375.3-rejected agents lts-candidate remoting robustness |