Best to upgrade to 2.10 if you’re not on it yet.
Cheers!
(Shameless plug) Every java main() method deserves http://picocli.info
> On Dec 15, 2017, at 8:45, Benjamin Jaton wrote:
>
> Oh interesting. Well this one appender is not async but it is multi
> threaded, so I think that explains it.
>
Oh interesting. Well this one appender is not async but it is multi
threaded, so I think that explains it.
Useful to know about 2031 though.
Thanks
Benjamin
On Thu, Dec 14, 2017 at 2:54 PM, Remko Popma wrote:
> Are you using Log4j 2.10?
> The reason I’m asking is that the 2.10 release contains
Are you using Log4j 2.10?
The reason I’m asking is that the 2.10 release contains a fix for
https://issues.apache.org/jira/browse/LOG4J2-2031.
Prior to 2.10, there was a possibility that log events ended up out of order in
the log when you’re using async loggers or async appender and the append
In a multi-threaded application it is entirely possible that log entries might
be appear to be out of order. This is because the LogEvent will populate the
timestamp field but then another thread might get control, generate its log
event, and then pass it to the appender before the first thread
Hello,
I am seeing logs that are not in order in the log file, it this expected
when using a RollingFile appender?
"appenders" : {
"appender" : [ {
"type" : "RollingFile",
"name" : "ServerAppender",
"PatternLayout" : {
"pattern" : "%d{-MM-dd HH:mm:ss,SS
Resource bundles contain localized text for internationalization purposes, not
configuration data. It is unfortunate that Sun chose to use the same properties
file format for resource bundles and properties files, but using the
PropertyResourceBundle class to read a property file is not somethin
