[
https://issues.apache.org/jira/browse/STORM-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381400#comment-14381400
]
ASF GitHub Bot commented on STORM-712:
--------------------------------------
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/468#issuecomment-86350235
@lazyval, sorry for delay in responding. We have seen this happen in case
some of our clusters. When the `ExecutorService`, executes the `FutureTask`, it
captures even `Error` and not processed by any thread's
`DefaultUnCaughtExceptionHandler`. This can lead to server not shutdown even
after OOM.
> Storm daemons must shutdown JVM in case of OOM in any thread
> ------------------------------------------------------------
>
> Key: STORM-712
> URL: https://issues.apache.org/jira/browse/STORM-712
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Kishor Patil
>
> In case of OutOfMemoryError in any thread, it needs to trigger immediate
> shutdown of the server. I can be done by using
> setDefaultUncaughtExceptionHandler on threads being created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
