[jira] [Comment Edited] (KAFKA-12699) Streams no longer overrides the java default uncaught exception handler

["Konstantine Karantasis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383586#comment-17383586 ] 

Konstantine Karantasis edited comment on KAFKA-12699 at 7/19/21, 9:08 PM:
--------------------------------------------------------------------------

Postponing to the subsequent release given that this issue is not a blocker and did not make it on time for the 3.0 code freeze. 


was (Author: kkonstantine):
Postponing to the subsequent release given that this issue is not a blocker and did not make it on time for 3.0 code freeze. 

> Streams no longer overrides the java default uncaught exception handler  
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-12699
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12699
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.8.0
>            Reporter: Walker Carlson
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> If a user used `Thread.setUncaughtExceptionHanlder()` to set the handler for all threads in the runtime streams would override that with its own handler. However since streams does not use the `Thread` handler anymore it will no longer do so. This can cause problems if the user does something like `System.exit(1)` in the handler. 
>  
> If using the old handler in streams it will still work as it used to



--
This message was sent by Atlassian Jira
(v8.3.4#803005)