You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2007/08/22 00:27:45 UTC

DO NOT REPLY [Bug 42023] - LoggingEvent Message Object is lost upon serialization

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42023>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42023


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From carnold@apache.org  2007-08-21 15:27 -------
I'm unclear whether you are saying the SocketAppender corrupts the original LoggingEvent so that other 
appenders can't access the original message object.  Basically, that you have a log4j configuration with a 
SocketAppender and your custom DBAppender and your DBAppender stops working when the 
SocketAppender is added. I reviewed the code and didn't see a mechanism for that to happen, but maybe I 
missed something.

If you are saying that a deserialized LoggingEvent (perhaps reconstituted by a SocketReceiver) is missing 
the original message, that is by design and would have to wait until 1.2.16 to be looked at since it would 
change the wire format for SocketAppender.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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