airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2363) Unable to configure logging with log4j.properties file
Date Mon, 10 Apr 2017 13:38:41 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962867#comment-15962867
] 

Marcus Christie commented on AIRAVATA-2363:
-------------------------------------------

[~adhamnas],

I'm fine with just using logback.  We already know it works with the Kafka integration. I
don't see any compelling reasons to use log4j 2.

> Unable to configure logging with log4j.properties file
> ------------------------------------------------------
>
>                 Key: AIRAVATA-2363
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2363
>             Project: Airavata
>          Issue Type: Bug
>          Components: Distribution
>    Affects Versions: 0.17
>            Reporter: Marcus Christie
>
> Currently, when starting Airavata, I see this on the console:
> {noformat}
> SLF4J: Found binding in [jar:file:/home/airavata/master-deployment/api-orchestrator/apache-airavata-server-0.17-SNAPSHOT/lib/logback-classic-1.1.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/home/airavata/master-deployment/api-orchestrator/apache-airavata-server-0.17-SNAPSHOT/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/home/airavata/master-deployment/api-orchestrator/apache-airavata-server-0.17-SNAPSHOT/lib/slf4j-simple-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> {noformat}
> This means that there are 3 different bindings for SLF4J. There should only be one.
> It also appears that it is picking up the logback binding, although unfortunately it
doesn't explicitly say so. I say that because I don't see any log4j messages when I add {{-Dlog4j.debug}}
as an argument.
> If I delete from the lib directory
> * logback-classic-1.1.6.jar
> * and slf4j-simple-1.7.25.jar
> Then slf4j uses log4j and the log4j.properties file in the bin/ directory is used for
configuration.
> As it stands right now, we are providing a log4j.properties file in the bin/ directory
of the distribution that doesn't actually do anything.  We should give users a way to configure
logging.
> I think there are a few options:
> * go with log4j12 logging
> ** the logback logging was added, I think, for the Kafka integration, so removing logback
would remove the Kafka integration
> * go with logback logging
> * switch to something else like log4j 2.x
> ** log4j 2 has Kafka integration, but I'm not sure how well it works



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message