You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2021/12/10 16:22:00 UTC
[jira] [Closed] (SLING-10973) osgi-mock: Generate Service Registration and Bundle IDs in a thread-safe way
[ https://issues.apache.org/jira/browse/SLING-10973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-10973.
----------------------------------
> osgi-mock: Generate Service Registration and Bundle IDs in a thread-safe way
> ----------------------------------------------------------------------------
>
> Key: SLING-10973
> URL: https://issues.apache.org/jira/browse/SLING-10973
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 3.2.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing OSGi Mock 3.2.2
>
>
> after a lot of debugging around a racing conditions which leads to services that are registered but not found afterwards in context of https://wcm-io.atlassian.net/browse/WTES-69 if found an actually issue in the way internal IDs for service registrations and bundle IDs are generated: an integer field with ++ used.
> osgi-mock is doing everything (except sending OSGi events) in a synchronous way. but if the actual code that is tested is using multiple threads, this can become a threading issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)