Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
scr-2.1.24
-
None
Description
I have observed the following exception when SCR is executing on one thread and another thread ends up uninstalling or unresolving one of the bundles SCR is processing. SCR should protect against this and fall back to the SCR logger instead of using the extendee bundle logger here.
java.lang.IllegalArgumentException: The bundle is not resolved: some.bundle.symbolic.name [128]
at org.eclipse.osgi.internal.log.ExtendedLogServiceImpl.getLogger(ExtendedLogServiceImpl.java:90)
at org.apache.felix.scr.impl.logger.LogManager$Lock.getLogger(LogManager.java:101)
at org.apache.felix.scr.impl.logger.LogManager$LoggerFacade.getLogger(LogManager.java:208)
at org.apache.felix.scr.impl.logger.ScrLogManager$ScrLoggerFacade.isLogEnabled(ScrLogManager.java:131)
at org.apache.felix.scr.impl.logger.ScrLogManager$ScrLoggerFacade.log(ScrLogManager.java:162)