You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Torgeir Veimo (JIRA)" <ji...@apache.org> on 2015/07/24 09:45:05 UTC
[jira] [Commented] (OAK-2736) Oak instance does not close the
executors created upon ContentRepository creation
[ https://issues.apache.org/jira/browse/OAK-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640091#comment-14640091 ]
Torgeir Veimo commented on OAK-2736:
------------------------------------
Running oak 1.3.3 now results in much less warnings during webapp restart. There is one remaining thread though that is not closed,
24-Jul-2015 17:41:06.727 WARNING [http-nio-8080-exec-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [frontend] appears to have started a thread named [oak-repository-executor-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
Am not sure if this one would be covered by this fix, or if something needs to be configured differently to get this thread to be stopped.
> Oak instance does not close the executors created upon ContentRepository creation
> ---------------------------------------------------------------------------------
>
> Key: OAK-2736
> URL: https://issues.apache.org/jira/browse/OAK-2736
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Labels: CI, Jenkins
> Fix For: 1.3.5
>
> Attachments: OAK-2736-2.patch, OAK-2736.patch
>
>
> Oak.createContentRepository does not closes the executors it creates upon close. It should close the executor if that is created by itself and not passed by outside
> Also see recent [thread|http://markmail.org/thread/rryydj7vpua5qbub].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)