[
https://issues.apache.org/jira/browse/SLING-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943292#comment-14943292
]
Robert Munteanu commented on SLING-5088:
----------------------------------------
And also
{noformat}java.lang.NullPointerException: null
at
org.apache.sling.testing.mock.osgi.MapUtil.propertiesMergeWithOsgiMetadata(MapUtil.java:57)
at
org.apache.sling.testing.mock.osgi.MockOsgi.deactivate(MockOsgi.java:192)
at
org.apache.sling.testing.mock.osgi.MockOsgi.deactivate(MockOsgi.java:182)
at
org.apache.sling.jcr.contentloader.internal.ContentLoaderServiceTest.cleanup(ContentLoaderServiceTest.java:78)
{noformat}
> 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 Jackrabbit 0.1.2, Testing Sling Mock
> 1.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Critical
> Labels: mocks
> Fix For: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock
> Oak 1.0.0, Testing OSGi Mock 1.6.0, 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)
