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

Ralph Goers commented on LOG4J2-96:
-----------------------------------

If I understand your previous message, you have two plugins that are each 
writing to the SocketServer.  Each of those plugins is isolated in its own 
bundle and so has its own SocketAppender and SocketManager. In that case what 
you are describing makes perfect sense and would be expected as the 
Appenders/Managers don't know about each other and think they are the only one 
writing to the socket. Given how ObjectOutputStream works I don't think you can 
use SerializedLayout. Instead we will have to use a different Serialization 
mechanism that doesn't differentiate between the first and subsequent objects.
                
> 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]

Reply via email to