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 2014/04/23 17:51:17 UTC
[jira] [Comment Edited] (LOG4J2-611) Logj 1.2 emulation is not
complete
[ https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978342#comment-13978342 ]
Ralph Goers edited comment on LOG4J2-611 at 4/23/14 3:50 PM:
-------------------------------------------------------------
Log4j 2 is not meant to completely "emulate" Log4j 1.x. The bridge is there primarily to allow users to use tools that log via Log4j 1.x to use Log4j 2. I notice that the class referenced above is trying to call logger.callAppenders as well (which is a noop in the bridge) and it is overriding the log methods in such a way that all the location information will be incorrect. Essentially it is trying to replace the underlying logging framework which is much more than the bridge is intended to support.
The "proper" solution would be to implement a Log4j2Factory that sits alongside Log4jFactory, SLF4JFactory, StandardLogFactory and NoLogFactory. I would suggest raising an issue with Hazelcast asking for Log4j 2 support.
was (Author: ralph.goers@dslextreme.com):
Log4j 2 is not meant to completely "emulate" Log4j 1.x. The bridge is there primarily to allow users to use tools that log via Log4j 1.x to use Log4j 2. I notice that the class referenced above is trying to call logger.callAppenders as well (which is a noop in the bridge) and it is overriding the log methods in such a way that all the location information will be incorrect. Essentially it is trying to replace the underlying logging framework which is much more than the bridge is intended to support.
The "proper" solution would be to implement a Log4j2Factory that sits alongside Log4jFactory, SLF4JFactory, StandardLogFactory and NoLogFactory.
> Logj 1.2 emulation is not complete
> ----------------------------------
>
> Key: LOG4J2-611
> URL: https://issues.apache.org/jira/browse/LOG4J2-611
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.0-rc1
> Reporter: Mikael Ståldal
>
> The class org.apache.log4j.spi.LoggingEvent is empty, which makes Hazelcast to fail since it tries to use this constructor:
> {{org.apache.log4j.spi.LoggingEvent.<init>(Ljava/lang/String;Lorg/apache/log4j/Category;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V}}
> It is used here (line 117):
> https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/logging/Log4jFactory.java
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org