Hi Remko,
If I don't disable the "Use an isolated class loader for this shared
library" option, then I get various ClassNotFoundException, such as
java.lang.ClassNotFoundException:
org.apache.logging.log4j.spi.AbstractLoggerAdapter. I tried moving logging
related JARs into the WAR one by one and e
What happens if you don't disable the "Use an isolated class loader for
this shared library" option? Is there an error message?
To go back to your original question:
it should be possible to have the log4j jars in the web container's shared
lib and let each web app have its own log4j2.xml config f
I got log separation to work by copying the log4j-core*.jar and
log4j-api-*.jar to the WAR's lib folder. We are using a Shared Library and
I also had to disable the option "Use an isolated class loader for this
shared library" for it to work.
However this is not ideal as disabling "Use an isolated
The manual (http://logging.apache.org/log4j/2.x/manual/logsep.html) says
you can follow step (3) below to get log separation. I am not clear on what
values to set for log4jContextName and log4jConfiguration, or how exactly
to do it on WebSphere 8.5 Has anyone done this? Really appreciate any help
i
Two quick questions: What is your log4j2 version, and are you using Async
Loggers?
On Fri, Nov 6, 2015 at 2:17 AM, Chinh Do wrote:
> Hi all,
>
> I am running multiple web apps (WARs) in the same WebSphere instance. Each
> web app has its own log4j2.xml and is configured to write to a separate lo
Hi all,
I am running multiple web apps (WARs) in the same WebSphere instance. Each
web app has its own log4j2.xml and is configured to write to a separate log
file. But I am seeing some log entries being written to the wrong log file.
I think the problem is because we are using the log4j JARs in
