[
https://issues.apache.org/jira/browse/CASSANDRA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-5273:
---------------------------------------
Attachment: 0001-CASSANDRA-5273-add-timeouts-to-the-blocking-commitlo.patch
adds a lock to make sure only one thread calls System.exit
the threads that would have called System.exit will block (unclear (to me) what
would happen if they would be allowed to continue to run where they should have
exited)
> 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
