[jira] [Commented] (LOG4J2-542) LogEvents with exceptions fail to deserialize

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916652#comment-13916652 ] 

Ralph Goers commented on LOG4J2-542:
------------------------------------

I suspect the best way to handle this is to add readObject and writeObject methods to ThrowableProxy.

> LogEvents with exceptions fail to deserialize
> ---------------------------------------------
>
>                 Key: LOG4J2-542
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-542
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.0-rc1
>            Reporter: Joern Huxhorn
>            Priority: Critical
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org