[
https://issues.apache.org/jira/browse/CASSANDRA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644517#comment-13644517
]
Jonathan Ellis commented on CASSANDRA-5273:
-------------------------------------------
bq. the threads that would have called System.exit
I don't think we're very rigorous about calling Thread.setDaemon, so I think
this will actually deadlock it -- System.exit will wait for daemon threads to
die, and the daemon threads will park at the lock acquisition.
> Hanging system after OutOfMemory. Server cannot die due to uncaughtException
> handling
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5273
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5273
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.1
> Environment: linux, 64 bit
> Reporter: Ignace Desimpel
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 1.2.5
>
> Attachments:
> 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch,
> 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch, CassHangs.txt
>
>
> On out of memory exception, there is an uncaughtexception handler that is
> calling System.exit(). However, multiple threads are calling this handler
> causing a deadlock and the server cannot stop working. See
> http://www.mail-archive.com/[email protected]/msg27898.html. And see
> stack trace in attachement.
--
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
