[
https://issues.apache.org/jira/browse/LOG4J2-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385372#comment-15385372
]
Remko Popma commented on LOG4J2-1468:
-------------------------------------
Wow, that is very detailed. I am beginning to understand the problem better
now, thanks!
I noticed log4j2 jar files seem to exist in two locations:
* some/path/WEB-INF/lib
* ear/path/APP-INF/lib
I am not sure if this could be related to the problem, but it may be worth
experimenting with having the log4j2 jars in only once place.
Another consideration is the SLF4J mention that "Logging calls were not
honored". This suggests to me that it may be a bug in SLF4J. Can you try using
the Log4j 2 API directly in these EJBs?
> 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
