Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
Description
The slave.jar should setup an UncaughtExceptionHandler to make it easier to diagnose things like NoClassDefFoundErrors which are impossible to debug once the original stack trace is lost.
Plan of action:
Remoting
Threads | Expected Behavior |
---|---|
SynchronousCommandTransport.ReaderThread | Log, terminate channel (see current generic error handling here) |
PortForwarder | Log, call close() |
CopyThread | Log |
Engine | Log, kill remoting |
PingThread | Log, call onDead(Throwable) |
Core
Threads | Expected Behavior |
---|---|
PlainCLIProtocol.EitherSide.Reader | |
TaskThread | |
ViewJob.ReloadThread | |
Executor | |
Proc.LocalProc.StdinCopyThread | |
AbstractNodeMonitorDescriptor.Record | |
TcpSlaveAgentListener | Log, call shutdown() |
TcpSlaveAgentListener.ConnectionHandler | Log, close socket |
UDPBroadcastThread | |
StreamCopyThread | |
AsynchronousAdministrativeMonitor.FixThread |
Attachments
Issue Links
- relates to
-
JENKINS-33395 Jenkins should install a default UncaughtExceptionHander
-
- Resolved
-
-
JENKINS-28499 tcpSlaveAgentListener not found
-
- Reopened
-
-
JENKINS-49415 Install additional UncaughtExceptionHandler in Engine
-
- Resolved
-
- links to
(1 links to)
Code changed in jenkins
User: Oleg Nenashev
Path:
pom.xml
http://jenkins-ci.org/commit/jenkins/013a64879601fe5c4e98552c28abfcff260f2202
Log:
Merge pull request #3061 from oleg-nenashev/remoting/3.13
[JENKINS-38711, JENKINS-47132] - Update Remoting to 3.13
Compare: https://github.com/jenkinsci/jenkins/compare/7a0d73e9ceb1...013a64879601