[
https://issues.jboss.org/browse/WFCORE-3336?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-3336:
---------------------------------------
Since the library doing the logging is a shared in the EAR it looks like when first
invoked it's seeing the log context from the first WAR in the EAR that uses it. This
should see whichever log context belongs to the EAR not either of the WAR's. What this
means is that any libraries in the EAR's {{lib}} directory should be using the
EAR's log context. In the case of the attached example the shared library should be
using the system log context since the EAR does not have a logging profile associated with
it.
Not able to separate application(EAR) logging with the use of logging
profile
-----------------------------------------------------------------------------
Key: WFCORE-3336
URL:
https://issues.jboss.org/browse/WFCORE-3336
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Attachments: 01933631-new.tar.gz
Two ear files are deployed on EAP instance and both are configured to use different
logging profile through EAR/META-INF/MANIFEST.MF file.
WAR file from EAR uses some libraries those are present in the "lib" folder of
each ear file. Application1.ear which logs in app1.log and Application2.ear which logs in
app2.log.
when we access application we can see logging from EAR1 into EAR2 log file .
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)