The stack trace information was not guaranteed to be stored correctly in previous releases of JBoss EAP 6. As a result, data could be lost upon serialization of Log4J logging events.
To fix this, Log4J has been amended to cache the stack trace (i.e. throwable information) upon deserialization. This ensures that stack trace information will not be lost upon serialization.
+++ This bug was initially created as a clone of Bug #1087630 +++
This is the only fix that is added (other than the System.out fix for bz 1070453) by taking the upgrade of log4j-jboss-logmanager from 1.0.2 to 1.1.0.
--- Additional comment from Kyle Lape on 2014-04-14 17:16:09 EDT ---
Since this BZ's component upgrade is already POST, I'm changing this to POST as well.
I simply can't determine from this BZ ticket or the associated git commit, the CCFR text, which is to appear in the Release Notes document. Please provide draft text that which can work on.
Verified with EAP 6.3.0.ER8
this issue is a clone of BZ 1087630 and Kyle provided the Doc Text there. I think you can use it, it is the same issue for different EAP version