Personally, I think you can make your life easier by not trying to replace
JsonLayout. Then you don’t have to worry about backward compatibility.
Alternatively, you could replace JsonLayout with a builder that uses the
existing configuration elements but creates your new Layout. If you do that
Hi,
Thank you very much for reply. Yes, "ExclusiveLock" works find. We will use
it instead as you suggested. It will work faster of course.
However, I still do not understand why "InterProcessLock" locking model
crashing the app. From my viewpoint it shouldn't. Maybe , I do not know
details how "
Why can't you use the default, ExclusiveLock? log4net automatically manages
writing messages from different threads in the same process. InterProcessLock
is for a specific use case where more than one process is trying to write to
the same file. In that case writing to multiple files and combin
Hi,
I have discovered a problem with "interprocesslock" locking model used in
our project for File appender. I will appreciate if you could investigate
the issue and let me know what is wrong. Maybe it is a bug within log4net
dll.
ISSUE:
If file appender is configured with
""
and
""
Then split
While replacing JsonLayout, I am a little bit puzzled by a certain issue,
which I will try to exemplify below:
LogstashLayout.Builder contains
- @PluginBuilderAttribute("prettyPrint") boolean prettyPrintEnabled;
- void isPrettyPrintEnabled()
- Builder setPrettyPrintEnabled(boolean prettyPrintEnabl
Given everybody is willing to give it a go, I've created LOG4J2-2764[1].
[1] https://issues.apache.org/jira/browse/LOG4J2-2764
On Mon, Jan 20, 2020 at 9:40 PM Volkan Yazıcı wrote:
>
> Given GitHub has introduced its own CI, i.e., GitHub Actions, would
> you consider migrating from Travis CI to t
