dlmarion commented on issue #2331: URL: https://github.com/apache/accumulo/issues/2331#issuecomment-957361677
> The uncaught handler that hlts seems to be setup by Threads.createThread(...). One possible way to make this not halt for client code is to move this to client context. So client context could have a create thread method that does not halt in the createThread method and server context could override createThread and halt in the uncaught handler. This makes sense, but then I would have to wire up the Context in all the places, possibly modifying even more code where a Thread is created but there is no reference to the Context. If we want to make it such that an Error does not halt the client VM, then it looks like the `SingletonManager.getMode()` might do what I need. `SingletonManager.setMode(Mode.SERVER)` is only called from `ServerInfo`. If the value is `Mode.SERVER`, then halt the VM on Error. Otherwise, just log the fact that the Thread has died. To be clear this would allow the Thread to die, as would happen prior to 2.1.0, in clients. This would not propagate the Error back to the caller so that they could handle the Error. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
