You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/10/13 02:31:03 UTC
[jira] [Comment Edited] (LOG4J2-98) Spring3 doesn't seem to work
with SLF4J (log4j2)
[ https://issues.apache.org/jira/browse/LOG4J2-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475464#comment-13475464 ]
Ralph Goers edited comment on LOG4J2-98 at 10/13/12 12:30 AM:
--------------------------------------------------------------
1. The default file name is log4j2.xml, not log4j.xml
2. debug, threshold and reset are not valid attributes for the configuration element - was there some documentation that had you add them that needs to be corrected? http://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSyntax documents the valid attributes.
3. You have a closing comment tag after the closing properties element and the closing List element but no opening comment.
was (Author: ralph.goers@dslextreme.com):
1. The default file name is log4j2.xml, not log4j.xml
2. threshold and reset are not valid attributes for the configuration element - was there some documentation that had you add them that needs to be corrected?
3. You have a closing comment tag after the closing properties element and the closing List element but no opening comment.
> Spring3 doesn't seem to work with SLF4J (log4j2)
> ------------------------------------------------
>
> Key: LOG4J2-98
> URL: https://issues.apache.org/jira/browse/LOG4J2-98
> Project: Log4j 2
> Issue Type: Bug
> Components: Flume Appender, SLF4J Bridge
> Affects Versions: 2.0-beta2
> Environment: Wicket, Spring 3, Log4j2, SLF4J, Tomcat 6.x
> Reporter: Amarkanth
> Fix For: 2.0-beta3
>
>
> I tried switching from log4j1.2 to log4j2 inorder to use the "Flume Appender" but i'm running into the following issue
> - The "log4j.xml" doesn't seem to get picked up
> - The application does start-up fine (but) there is no logging.
> Prior to the migration, the logging worked fine.
> I have the following config (pom.xml)
> =============================
> <dependency>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-api</artifactId>
> <version>2.0-beta2</version>
> </dependency>
> <dependency>
> <groupId>org.apache.logging.log4j</groupId>
> <artifactId>log4j-core</artifactId>
> <version>2.0-beta2</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-api</artifactId>
> <version>1.7.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.logging.log4j.adapters</groupId>
> <artifactId>slf4j-impl</artifactId>
> <version>2.0-beta2</version>
> </dependency>
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>jcl-over-slf4j</artifactId>
> <version>1.7.0</version>
> <scope>runtime</scope>
> </dependency>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org