Re: Attempting to change consumers of Log4j 2 SerializedLayout

I updated the JMS integration tests away from SerializedLayout. Gary On Fri, Jun 30, 2017 at 7:41 AM, Matt Sicker wrote: > The JMS appender supported it by default, so any configurations set up to > append to JMS and read them elsewhere as objects won't work by default >

Re: Attempting to change consumers of Log4j 2 SerializedLayout

Chainsaw supports log4j1's xml format over UDP and TCP, as well as any regular text format via (VFS)LogFilePatternReceiver. It also supports log4j1's serialized loggingevent format. Chainsaw integration with Logj42 is via VFSLogFilePatternReceiver - you have to specify the pattern and an

Re: Attempting to change consumers of Log4j 2 SerializedLayout

The JMS appender supported it by default, so any configurations set up to append to JMS and read them elsewhere as objects won't work by default anymore, though that's somewhat a custom config more so than an application. On 30 June 2017 at 08:56, Mikael Ståldal wrote: > Now

Attempting to change consumers of Log4j 2 SerializedLayout

Now when we have deprecated SerializedLayout, we should attempt to get all known consumers of it to be changed to instead/also support JsonLayout (or something else if more appropriate). The Socket Server in Log4j already support JsonLayout and XmlLayout as well, and I have just changed it to