[SLING-5088] sling-mock: Threads created by resource resolver/JCR are not terminated properly

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Testing Sling Mock Jackrabbit 0.1.2, Testing Sling Mock 1.5.0
• Fix Version/s: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock 1.6.0, Testing Sling Mock Oak 1.0.0, Testing OSGi Mock 1.6.0
• Component/s: Testing
• Labels: mocks
• Assignee: Stefan Seifert
• Reporter: Stefan Seifert
• Created: 02/Oct/15 16:29
• Updated: 26/Oct/15 16:00
• Resolved: 02/Oct/15 22:44

Description

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.

Issue Links

• is related to: SLING-5091 JCR Content Loader Unit Tests do not run with latest sling-mock-oak
• is related to: SLING-5197 sling-mock: Do not override ResourceResolverFactoryActivator's default values
• is related to: SLING-5090 osgi-mock: Support ServiceFactory
• relates to: SLING-5067 sling-mock: "uniqueRoot()" to simplify creation and cleanup of unique root paths in repository
• relates to: SLING-5089 mock-osgi: Deactivate all services on shutdown