Log4j 2
  1. Log4j 2
  2. LOG4J2-542

LogEvents with exceptions fail to deserialize

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-rc1
    • Fix Version/s: 2.0-rc2
    • Component/s: Appenders
    • Labels:
      None

      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.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Ralph Goers
              Reporter:
              Joern Huxhorn
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development