You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "David Jacot (Jira)" <ji...@apache.org> on 2021/11/15 10:11:00 UTC

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

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

David Jacot commented on KAFKA-12699:
-------------------------------------

Moving to the next release as we are past the 3.1 release 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.1.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.20.1#820001)