[
https://issues.apache.org/jira/browse/BOOKKEEPER-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716535#comment-13716535
]
Ivan Kelly commented on BOOKKEEPER-625:
---------------------------------------
I wasn't suggesting that we catch and log and stop there. We should catch, log
and then break out of the loop. That way there will be something in the server
log and not just the console.
> On OutOfMemoryError in NIOServerFactory thread bookie should shutdown
> ---------------------------------------------------------------------
>
> Key: BOOKKEEPER-625
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-625
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.1
> Reporter: Vinay
> Assignee: Vinay
> Fix For: 4.2.2
>
> Attachments: BOOKKEEPER-625-branch-4.2.patch
>
>
> Observed OutOfMemoryError in NIOServerFactory, but it didnt bring down the
> bookie and it continued to run without serving.
> On OOME in any thread, bookie should shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
