This version of Lilith demands Java 8 update 181 or higher and will says so if you try to start it with an older version. It has also been built and tested with Java 10.0.2.
You can still receive event from previous versions so if your
application is still running Java 7 or lower just keep using the
0.9.44 artifacts.
Keep in mind that
Java
SE 7 End of Public Updates has already been reached.
JsonLayout
, YamlLayout
and XmlLayout
. SerializedLayout
has been deprecated in log4j2 2.9.0 so you should use one of the other options instead.1.8.0_181
.null
event when end of stream was reached.logback-access
does not have an AccessEventVO
. See also LOGBACK-1182 - Problem deserializing AccessEvent..de.huxhorn.lilith.logback.appender.ClassicMultiplexSocketAppender
and de.huxhorn.lilith.logback.encoder.ClassicLilithEncoder
have not been moved. de.huxhorn.lilith.logback.encoder.AccessLilithEncoder
changed to de.huxhorn.lilith.logback.encoder.access.AccessLilithEncoder
.de.huxhorn.lilith.logback.appender.AccessMultiplexSocketAppender
changed to de.huxhorn.lilith.logback.appender.access.AccessMultiplexSocketAppender
.de.huxhorn.lilith.logback.appender.ClassicJsonMultiplexSocketAppender
changed to de.huxhorn.lilith.logback.appender.json.ClassicJsonMultiplexSocketAppender
.de.huxhorn.lilith.logback.appender.ZeroDelimitedClassicJsonMultiplexSocketAppender
changed to de.huxhorn.lilith.logback.appender.json.ZeroDelimitedClassicJsonMultiplexSocketAppender
.de.huxhorn.lilith.logback.appender.ClassicXmlMultiplexSocketAppender
changed to de.huxhorn.lilith.logback.appender.xml.ClassicXmlMultiplexSocketAppender
.de.huxhorn.lilith.logback.appender.ZeroDelimitedClassicXmlMultiplexSocketAppender
changed to de.huxhorn.lilith.logback.appender.xml.ZeroDelimitedClassicXmlMultiplexSocketAppender
.AccessEvent
sent by SocketAppender
isn't guaranteed to be deserializable at the moment. You can use the Lilith Multiplex Socket Appender in the meantime.
See LOGBACK-1182 - Problem deserializing AccessEvent..append=false
.ClassLoaderName
, ModuleName
and ModuleVersion
for the call location of the event. Search LOG4J_MODULE
in the source to take a look at the problem. Since Log4j 1 End-Of-Life has been announced 2015-08-06, chances are pretty slim that this will be fixed. Upgrade to log4j 2 or Logback.
Donate in Bitcoin. - 3MwD28iwF3faSvKUBYNe2XuCzStBi1NzAH
Donate in Bitcoin Cash. - qptxwv5la2war4v67f3yf47cxj59ca2s5vh4jz0tt9
Donate in Zcash. - t1TLsUKLsNczQbG4PVx7iNEyP5LtKauL3gr
Donate in Litecoin. - MPYHQnhjtv9nVFCoHF3UyPJAvhwqqZ2snx