[
https://issues.apache.org/jira/browse/LOG4J2-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487803#comment-13487803
]
Robert Breunung commented on LOG4J2-96:
---------------------------------------
I will try to build a minimal example for you. I think the problem might be
connected with different class loaders from different plugins. The Logger
worked for multiple (2) Messages from the same plugin, but stopped after a
class from another plugin also tried to use it.
I will write a second comment later, after reviewing the problem again.
> Error with SocketServer
> -----------------------
>
> Key: LOG4J2-96
> URL: https://issues.apache.org/jira/browse/LOG4J2-96
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-beta1
> Reporter: Robert Breunung
> Assignee: Ralph Goers
> Labels: appender, layout, server, socket
>
> Hello,
> by using your core.appender.SocketAppender and your core.netSocketServer I
> found a dissent.
> I am using the default setup of the appender with the SerializedLayout. The
> first send event to the server is properly deserialized. on the second I get
> an IOException:
> log4j java.io.StreamCorruptedException: invalid type code: AC
> I researched the problem and I found a solution here:
> http://stackoverflow.com/questions/2393179/streamcorruptedexception-invalid-type-code-ac
> The appender creates a new output stream for each log event. It writes every
> time a header. The listening server don't expect a header the second time.
> Because of this it crashes.
> Sincerely
> Robert Breunung
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
