[
https://issues.apache.org/jira/browse/GEODE-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989612#comment-15989612
]
ASF subversion and git services commented on GEODE-2811:
--------------------------------------------------------
Commit 7948362fbd0422b01de429906a9cc51348c5f7aa in geode's branch
refs/heads/feature/GEODE-2852 from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=7948362 ]
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
> Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Labels: storage_2
> Fix For: 1.2.0
>
>
> 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)
