[
https://issues.apache.org/jira/browse/SLING-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941149#comment-14941149
]
Robert Munteanu commented on SLING-5067:
----------------------------------------
Right now I can only provide the result of
{noformat}$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 127107
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1200
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
{noformat}
I guess {{ulimit -u}} is what interests you here. As a way of debugging, maybe
you can monitor the number of threads started in the surefire process? That
would indicate if there is indeed a problem.
> 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)
