[
https://issues.apache.org/jira/browse/LOG4J2-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385467#comment-15385467
]
Sawan Patwari commented on LOG4J2-1468:
---------------------------------------
Hi Remko,
Don't worry about the jar files being present at the location
'some/path/WEB-INF/lib', they are just placed there in the project in eclipse.
Neither WAR file is part of the EAR file nor it is deployed onto the Weblogic
12C server. It is only the EAR file that is deployed on the server. The
scenario that I presented works wonders if we use the below jars as I pointed
out in the issue description:
1. slf4j-api-1.7.21
2. slf4j-log4j12-1.7.21
3. log4j-1.2.17
But, the very same scenario fails when we use the below jars as part of Log4j2
upgradation.
1. log4j-api-2.6.2.jar
2. log4j-core-2.6.2.jar
3. log4j-slf4j-impl-2.6.2.jar
4. slf4j-api-1.7.21.jar
As far as SLF4j is concerned, the same scenario failed when using Log4j 1.x
with the below jars combination. There was an issue with SLF4j version 1.7.5,
which they fixed it and the same scenario worked fine with an upgradation to
SLF4j version 1.7.21, currently, the one which we are using with Log4j 1.x in
out test environment.
1. slf4j-api-1.7.5
2. slf4j-log4j12-1.7.5
3. log4j-1.2.17
The difference between using Log4j 1.x and Log4j 2.x is inclusion of
'log4j-slf4j-impl-2.6.2.jar', which is from Log4j, but isn't from SLF4j unlike
in case of Log4j 1.x usage, where we used slf4j-log4j12-1.7.21 jar.
I can try Log4j 2 API directly in these EJBs for testing purposes. But, this
wouldn't be the correct environment for the scenario that is under scrutiny.
My gut feeling says that there is an issue on Log4j 2.x with respect to
concurrency log calls during Initialisation phase. If Log4j 2.x has to be
independent of SLF4j then this failed scenario must be examined.
Regards,
-Sawan.Patwari
> EJBs' Concurrent Initilization Phase Logs Issue
> -----------------------------------------------
>
> Key: LOG4J2-1468
> URL: https://issues.apache.org/jira/browse/LOG4J2-1468
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.6.2
> Environment: Windows, Weblogic Server 12C, and JDK 1.8.
> Reporter: Sawan Patwari
> Attachments: Log4j2.x Upgradation Issue Information.docx
>
>
> An EAR file has two EJB components. Each of the components do log4j
> Info-logging at the time of ejb creation. The issue is that when this EAR
> file deployed onto the server, the Info-loggings are not captured in the log
> file from both the EJB beans.
> We are using below jars:
> 1. log4j-api-2.6.2.jar
> 2. log4j-core-2.6.2.jar
> 3. log4j-slf4j-impl-2.6.2.jar
> 4. slf4j-api-1.7.21.jar
> There was no issue when we used the below jars:
> 1. slf4j-api-1.7.21
> 2. slf4j-log4j12-1.7.21
> 3. log4j-1.2.17
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
