[
https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143606#comment-17143606
]
David Leangen commented on JAMES-3239:
--------------------------------------
There is quite a bit of chatter about the logging system itself at startup. I
get the impression that there is something confusing about logging going on
here.
[~btellier], any thoughts?
{noformat}
james_1 | 06:28:52,306 |-INFO in ch.qos.logback.classic.LoggerContext[default]
- Could NOT find resource
[/opt/apache-james/james-basic-server/conf/logback.xml]
james_1 | 06:28:52,307 |-INFO in ch.qos.logback.classic.LoggerContext[default]
- Could NOT find resource [logback-test.xml]
james_1 | 06:28:52,308 |-INFO in ch.qos.logback.classic.LoggerContext[default]
- Could NOT find resource [logback.groovy]
james_1 | 06:28:52,309 |-INFO in ch.qos.logback.classic.LoggerContext[default]
- Found resource [logback.xml] at
[jar:file:/opt/apache-james/james-basic-server/lib/james-server-jpa-guice-3.6.0-SNAPSHOT.jar!/logback.xml]
james_1 | 06:28:52,337 |-INFO in
ch.qos.logback.core.joran.spi.ConfigurationWatchList@3a52dba3 - URL
[jar:file:/opt/apache-james/james-basic-server/lib/james-server-jpa-guice-3.6.0-SNAPSHOT.jar!/logback.xml]
is not of type file
james_1 | 06:28:52,556 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not
set
james_1 | 06:28:52,558 |-INFO in
ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding
LoggerContextListener of type
[ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
james_1 | 06:28:52,612 |-INFO in
ch.qos.logback.classic.jul.LevelChangePropagator@2a5c8d3f - Propagating DEBUG
level on Logger[ROOT] onto the JUL framework
james_1 | 06:28:52,613 |-INFO in
ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting
LoggerContextListener
james_1 | 06:28:52,613 |-INFO in
ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender
of type [ch.qos.logback.core.ConsoleAppender]
james_1 | 06:28:52,619 |-INFO in
ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CONSOLE]
james_1 | 06:28:52,623 |-INFO in
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default
type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder]
property
james_1 | 06:28:52,628 |-WARN in
ch.qos.logback.classic.encoder.PatternLayoutEncoder@752325ad - As of version
1.2.0 "immediateFlush" property should be set within the enclosing Appender.
james_1 | 06:28:52,628 |-WARN in
ch.qos.logback.classic.encoder.PatternLayoutEncoder@752325ad - Please move
"immediateFlush" property into the enclosing appender.
james_1 | 06:28:52,728 |-WARN in
ch.qos.logback.classic.encoder.PatternLayoutEncoder@752325ad - Setting the
"immediateFlush" property of the enclosing appender to false
james_1 | 06:28:52,730 |-INFO in
ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT
logger to WARN
james_1 | 06:28:52,730 |-INFO in
ch.qos.logback.classic.jul.LevelChangePropagator@2a5c8d3f - Propagating WARN
level on Logger[ROOT] onto the JUL framework
james_1 | 06:28:52,730 |-INFO in
ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named
[CONSOLE] to Logger[ROOT]
james_1 | 06:28:52,732 |-INFO in
ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger
[org.apache.james] to INFO
james_1 | 06:28:52,732 |-INFO in
ch.qos.logback.classic.jul.LevelChangePropagator@2a5c8d3f - Propagating INFO
level on Logger[org.apache.james] onto the JUL framework
james_1 | 06:28:52,733 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
james_1 | 06:28:52,736 |-INFO in
ch.qos.logback.classic.joran.JoranConfigurator@279fedbd - Registering current
configuration as safe fallback point
{noformat}
> Clarify Logging Configuration (logback.xml & log4j.properties)
> --------------------------------------------------------------
>
> Key: JAMES-3239
> URL: https://issues.apache.org/jira/browse/JAMES-3239
> Project: James Server
> Issue Type: Sub-task
> Reporter: David Leangen
> Priority: Major
>
> In the context of the *Basic Server*, determine if (1) this configuration is
> necessary, and if so (2) how can we minimize it and (3) document it better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
