[
https://issues.apache.org/jira/browse/SLING-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943286#comment-14943286
]
Robert Munteanu commented on SLING-5088:
----------------------------------------
This might've caused test errors in the {{bundles/jcr/contentloader}} module.
The shared stack trace seems to be
{noformat}java.lang.RuntimeException: Unable to invoke method 'activate' for
class
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory
at
org.apache.sling.testing.mock.sling.oak.OakMockSlingRepository.login(OakMockSlingRepository.java:105)
at
org.apache.sling.testing.mock.sling.oak.OakMockSlingRepository.loginAdministrative(OakMockSlingRepository.java:121)
at
org.apache.sling.jcr.resource.internal.JcrResourceListener.<init>(JcrResourceListener.java:118)
at
org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProviderFactory.activate(JcrResourceProviderFactory.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.apache.sling.testing.mock.osgi.OsgiServiceUtil.invokeMethod(OsgiServiceUtil.java:253)
at
org.apache.sling.testing.mock.osgi.OsgiServiceUtil.activateDeactivate(OsgiServiceUtil.java:86)
at
org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:162)
at
org.apache.sling.testing.mock.osgi.MockOsgi.activate(MockOsgi.java:173)
at
org.apache.sling.testing.mock.sling.MockJcrResourceResolverFactory.getResourceResolverInternal(MockJcrResourceResolverFactory.java:67)
at
org.apache.sling.testing.mock.sling.AbstractMockResourceResolverFactory.getAdministrativeResourceResolver(AbstractMockResourceResolverFactory.java:106)
at
org.apache.sling.testing.mock.sling.context.SlingContextImpl.resourceResolver(SlingContextImpl.java:179)
at
org.apache.sling.jcr.contentloader.internal.ContentLoaderServiceTest.setup(ContentLoaderServiceTest.java:61)
{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)
