Critical Description
Events serialized by
<Socket name="Socket" host="localhost" port="4560" protocol="TCP">
<SerializedLayout />
</Socket>
are suddenly containing unchanged serialized exceptions again. This was already working in earlier versions.
Doing so means that receiving such log-events is impossible if the exception class is not available in the receiving application. This is the main reason for ThrowableProxy.
This is caused by
org.apache.logging.log4j.core.impl
public class ThrowableProxy {
private final Throwable throwable;
}
The throwable field would have to be transient and the info of the Throwable would have to be added to ThrowableProxy. This may be the only necessary change but I'm not sure.
Attachments
Issue Links
- is related to
-
LOG4J2-299 Ability to retrieve original Throwable from ThrowableProxy
-
- Closed
-
-
-
- Resolved
-