Yes, that blog post is incorrect. The blog post links to our Jira issue. I
have updated that to add the recommendation that user’s use JsonLayout and
mention that the SocketServers are still supported.
The blog post doesn’t allow comments and I see no other way to correct them. It
is rather an
Elasic.co got it wrong in that blog post. The problem is not
SockerAppender, the problem is SerializedLayout.
Maybe people were confusing the two, since SerializedLayout used to be
default layout for SockerAppender. But it has always been possible to
configure SockerAppender to use another lay
If you want to use the SocketAppender, I'd recommending adding the
appropriate Jackson dependencies and using the JSON layout. I have a desire
to eventually implement a similar layout using Apache Avro and/or Apache
Thrift which would be a lot faster, though either way, just stick with
anything oth
Thanks for your response.
--
Sent from: http://apache-logging.6191.n7.nabble.com/Log4j-Users-f4.html
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: log4j-user-h...@logging.
There are no plans to deprecate socket appenders. We only recommend the
SerializedLayout not be used. We moved the Socket server out of core because it
is meant to be a sample for users to modify to meet their needs, not really use
as is.
Ralph
> On Oct 23, 2017, at 11:25 PM, "[email protected]
