-
Bug
-
Resolution: Fixed
-
Minor
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 |
- relates to
-
-
- Resolved
-
-
-
- Reopened
-
-
-
- Resolved
-
- links to
(1 links to)
