[
https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978364#comment-13978364
]
Mikael Ståldal commented on LOG4J2-611:
---------------------------------------
Well, I would say that Hazelcast _is_ a tool that log via Log4j 1.x. But
perhaps Hazelcast is abusing the Log4j 1.x API.
However, I tried to configure Hazelcast to use SLF4J instead, and injected the
SLF4J bridge to Log4J 2. And that seems to work. So problem solved for me.
> 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: [email protected]
For additional commands, e-mail: [email protected]
