Log4j creates an empty log file and refuses to fill it?

[i-make-robots]

Hello, everyone. I hope you're doing well.

My Java 22 open source project is https://github.com/MarginallyClever/Makelangelo-software/.
I'm using logback and log4j with a rolling file appender. My config file is https://github.com/MarginallyClever/Makelangelo-software/blob/master/src/main/resources/logback.xml
I then use JPackage to distribute my app with all the dependencies baked into a fat jar.

For MOST people the log file appears and fills normally. For a select number of users the log file appears but stays empty.
They have been gracious enough to try running the JAR from the command line but we've seen no extra console messages.
Running in administrator mode doesn't help.
Immediate flushing doesn't help.
Adding a logback status listener (logback-status.log) also doesn't appear for those tricky users.

Can someone please give me a hint what I'm doing wrong?

[ppkarwasz]

Hi @i-make-robots,

My Java 22 open source project is https://github.com/MarginallyClever/Makelangelo-software/. I'm using logback and log4j with a rolling file appender.

After reviewing your repository, it appears that the project uses SLF4J as the logging API and Logback as the underlying implementation. It doesn't use neither the Log4j 2 API nor its Log4j Core implementation.

Since your setup is based on Logback rather than Log4j 2, you'd likely get more relevant support by posting your question in the Logback Discussions page.

Hope this helps!

[i-make-robots]

Whoops.