[
https://issues.apache.org/jira/browse/SLING-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941973#comment-14941973
]
Stefan Seifert commented on SLING-5088:
---------------------------------------
rev. 1706506
there where misc. executor services left in oak and osgi-mock that were not
closed properly. fixed no. thead list in sling-mock is not completely clean
after all unit tests completed. marked some methods in MockSling and MockOsgi
as deprecated which usage may lead to memory leaks because bundle context
cannot be shut down properly.
> 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)
