[ https://issues.apache.org/jira/browse/SLING-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-5088. ----------------------------------- Resolution: Fixed rev. 1706500 should be fixed for sling-mock. no threads kept open exception some JDK-internal ThreadPoolExecutor pool items. the code for setting up ResourceResolverFactoryActivator is much cleaner now and more correct than before. will have to look separately at sling-mock-oak. > sling-mock: Threads created by resource resolver/JCR are not terminated > properly > -------------------------------------------------------------------------------- > > Key: SLING-5088 > URL: https://issues.apache.org/jira/browse/SLING-5088 > Project: Sling > Issue Type: Bug > Components: Testing > Affects Versions: Testing Sling Mock 1.5.0 > Reporter: Stefan Seifert > Assignee: Stefan Seifert > Priority: Critical > Labels: mocks > Fix For: Testing Sling Mock 1.6.0 > > > as detected in SLING-5067 threads that are opened during unit test run when > setting up resource resolver with JCR mapping for the mocks are not > terminated properly and may lead to problems if the number of unit tests > increases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)