[
https://issues.apache.org/jira/browse/GEODE-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987183#comment-15987183
]
ASF subversion and git services commented on GEODE-2811:
--------------------------------------------------------
Commit bee0b7d570f62848318ffcd719efaee6e5884102 in geode's branch
refs/heads/develop from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=bee0b7d ]
GEODE-2811: close OffHeapEvictor when cache is closed
Rejected executions are now ignored if shutting down.
execute now used instead of submit.
Close logic on HeapEvictor improved to prevent race conditions and NPEs.
> Thread leak when offheap memory is configured
> ---------------------------------------------
>
> Key: GEODE-2811
> URL: https://issues.apache.org/jira/browse/GEODE-2811
> Project: Geode
> Issue Type: Bug
> Components: offheap
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Labels: storage_2
>
> If you are using offheap memory and keep creating and close the cache over
> and over then you may run out of threads.
> Each time the cache is initialized it creates a thread pool to handle offheap
> LRU eviction. The thread pool should be closed when the cache is closed but
> is not.
> The can lead to an exception like this:
> {quote}
> java.lang.OutOfMemoryError: unable to create new native thread
> {quote}
> The threads will be cleaned up if the garbage collector has a major enough
> collection to force java object finalization but that may never happen since
> offheap is being used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
