[
https://issues.apache.org/jira/browse/SLING-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940459#comment-14940459
]
Robert Munteanu commented on SLING-5067:
----------------------------------------
[~sseif...@pro-vision.de] - the mock tests have recently started to fail for
me, e.g. with
{noformat}Exception in thread "oak-scheduled-executor-3"
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at
java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
at
java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1018)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745){noformat}
I don't expect to fail for someone else, my laptop intentionally has a low
process limit to catch these kinds of things :-)
git bisect indicates that this is the bad commit
{noformat}3ead30640692c1d387703e1f5c966c01f47d911b is the first bad commit
commit 3ead30640692c1d387703e1f5c966c01f47d911b
Author: Stefan Seifert <sseif...@apache.org>
Date: Sun Sep 27 09:46:11 2015 +0000
SLING-5067 sling-mock: "uniqueRoot()" to simplify creation and cleanup of
unique root paths in repository
git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1705520
13f79535-47bb-0310-9956-ffa450edef68
:040000 040000 c685db6473c73ba8a09682e691c69ec7a82d4fd8
53f1cf2e6a2c51b6b387cad3deb24008d8b1f9f1 M testing{noformat}
Can you take a look and see whether there are some leaks?
I would expect that an unclosed Oak repository causes this issue, as it
internally starts some threads which are only cleaned up at shutdown. If the
repository is not shutdown then those threads will stay alive, exhausting all
available processes for my user -> OutOfMemoryError
> sling-mock: "uniqueRoot()" to simplify creation and cleanup of unique root
> paths in repository
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-5067
> URL: https://issues.apache.org/jira/browse/SLING-5067
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Affects Versions: Testing Sling Mock 1.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock
> Oak 1.0.0, Testing Sling Mock 1.6.0
>
>
> when using resource resolver types JCR_JACKRABBIT and JCR_OAK unique root
> paths have to be used because the repository is not cleaned up after each
> run, and esp. if unit tests run in parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
