You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Roland Jungnickel (JIRA)" <ji...@apache.org> on 2016/06/14 17:53:27 UTC
[jira] [Updated] (STORM-1900) Log configuration with logback
[ https://issues.apache.org/jira/browse/STORM-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Jungnickel updated STORM-1900:
-------------------------------------
Description:
I am trying to use logback in my project and am getting this message:
{quote}
2016-06-14 16:55:56.945 STDERR [INFO] SLF4J: Class path contains multiple SLF4J bindings.
2016-06-14 16:55:56.997 STDERR [INFO] SLF4J: Found binding in [jar:file:/opt/apache-storm-0.10.1/lib/log4j-slf4j-impl-2.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Found binding in [jar:file:/srv/storm/supervisor/stormdist/MatchIdentifiers-675106f-1465923070-5-1465923118/stormjar.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
2016-06-14 16:56:03.647 STDERR [INFO] 2016-06-14 16:56:03,641 ERROR Logger contains an invalid element or attribute "appender"{quote}
The solution slf4j suggests is to exclude slf4j from the dependency which in this case would be storm. But since storm includes slf4j in the classpath when starting the topology this does not work. Is there a known way to fix this?
was:
I am trying to use logback in my project and am getting this message:
2016-06-14 16:55:56.945 STDERR [INFO] SLF4J: Class path contains multiple SLF4J bindings.
2016-06-14 16:55:56.997 STDERR [INFO] SLF4J: Found binding in [jar:file:/opt/apache-storm-0.10.1/lib/log4j-slf4j-impl-2.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Found binding in [jar:file:/srv/storm/supervisor/stormdist/MatchIdentifiers-675106f-1465923070-5-1465923118/stormjar.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
2016-06-14 16:56:03.647 STDERR [INFO] 2016-06-14 16:56:03,641 ERROR Logger contains an invalid element or attribute "appender"
The solution slf4j suggests is to exclude slf4j from the dependency which in this case would be storm. But since storm includes slf4j in the classpath when starting the topology this does not work. Is there a known way to fix this?
> Log configuration with logback
> ------------------------------
>
> Key: STORM-1900
> URL: https://issues.apache.org/jira/browse/STORM-1900
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.10.1
> Reporter: Roland Jungnickel
>
> I am trying to use logback in my project and am getting this message:
> {quote}
> 2016-06-14 16:55:56.945 STDERR [INFO] SLF4J: Class path contains multiple SLF4J bindings.
> 2016-06-14 16:55:56.997 STDERR [INFO] SLF4J: Found binding in [jar:file:/opt/apache-storm-0.10.1/lib/log4j-slf4j-impl-2.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> 2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Found binding in [jar:file:/srv/storm/supervisor/stormdist/MatchIdentifiers-675106f-1465923070-5-1465923118/stormjar.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> 2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> 2016-06-14 16:55:56.998 STDERR [INFO] SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> 2016-06-14 16:56:03.647 STDERR [INFO] 2016-06-14 16:56:03,641 ERROR Logger contains an invalid element or attribute "appender"{quote}
> The solution slf4j suggests is to exclude slf4j from the dependency which in this case would be storm. But since storm includes slf4j in the classpath when starting the topology this does not work. Is there a known way to fix this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)