You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2021/02/24 15:18:00 UTC
[jira] [Comment Edited] (UIMA-6303) Logs are spammed with "Import
by location/name" messages
[ https://issues.apache.org/jira/browse/UIMA-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289971#comment-17289971 ]
Richard Eckart de Castilho edited comment on UIMA-6303 at 2/24/21, 3:17 PM:
----------------------------------------------------------------------------
The relevant code seems to be this:
*Slf4jLogger_impl:180*
{noformat}
case org.apache.uima.util.Level.CONFIG_INT:
return logger.isInfoEnabled(UIMA_MARKER_CONFIG);
{noformat}
If I understand it correctly, this say that stuff logged in the UIMA {{CONFIG_INT}} level should only be logged if logging for the marker {{UIMA_MARKER_CONFIG}} is enabled. Unfortunately, not all loggers support markers. E.g. the SLF4J SimpleLogger simply logs the stuff and discards the marker.
was (Author: rec):
The relevant code seems to be this:
*Slf4jLogger_impl:180*
```
case org.apache.uima.util.Level.CONFIG_INT:
return logger.isInfoEnabled(UIMA_MARKER_CONFIG);
```
If I understand it correctly, this say that stuff logged in the UIMA {{CONFIG_INT}} level should only be logged if logging for the marker {{UIMA_MARKER_CONFIG}} is enabled. Unfortunately, not all loggers support markers. E.g. the SLF4J SimpleLogger simply logs the stuff and discards the marker.
> Logs are spammed with "Import by location/name" messages
> --------------------------------------------------------
>
> Key: UIMA-6303
> URL: https://issues.apache.org/jira/browse/UIMA-6303
> Project: UIMA
> Issue Type: Bug
> Components: uimaj
> Affects Versions: 3.1.1SDK
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
> Fix For: 3.2.0SDK
>
>
> The CONFIG logging level of UIMA is mapped to the INFO level of SLF4J. This causes all kinds of configuration information to be logged at INFO level (e.g. components being initialized)... but it also causes all "Import by name/location" messages to be logged at info level. If you work with non-trivial type systems that import other type systems, this can very quickly become *really* annoying.
> I see this in the v3 branch mainly. Looking at the v2 branch, I can see that CONFIG is also mapped to INFO there for the log4j logger - no idea why it never annoyed me with v2. I don't remember having seen any such messages. Need to check...
> So there are two options:
> - map CONFIG to DEBUG
> - demote the "Import by..." messages from CONFIG to FINE (FINE == DEBUG)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)