You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tom Watson (Jira)" <ji...@apache.org> on 2020/11/20 20:57:00 UTC
[jira] [Assigned] (FELIX-6361) IllegalArgumentException possible
from LoggerFactory.getLogger(Bundle, String, Class)
[ https://issues.apache.org/jira/browse/FELIX-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Watson reassigned FELIX-6361:
---------------------------------
Assignee: Tom Watson
> IllegalArgumentException possible from LoggerFactory.getLogger(Bundle, String, Class<L>)
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-6361
> URL: https://issues.apache.org/jira/browse/FELIX-6361
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.1.24
> Reporter: Tom Watson
> Assignee: Tom Watson
> Priority: Major
> Fix For: scr-2.1.26
>
>
> 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)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)