Logging is completely turned off unintentionally via UI

[zfarrell]

Description

---

Recently, my team had to debug an issue where we were no longer getting any output in the server logs. I'm fairly confident this happened after adding a new logger setting (Configurations -> server-config ->Logger Settings -> Add Logger) and saving.

My colleague ended up solving this by discovering that com.sun.enterprise.server.logging.GFFileHandler had been set to "OFF". Changing this back to "INFO" resolved the issue.

Expected Outcome

Log levels should not change unexpectedly.

Steps to reproduce (Only for bug reports)

While we've had it happen to us multiple times, we're not sure what exact steps cause it to reproduce.

I'm fairly confident this happened after adding a new logger setting (Configurations -> server-config ->Logger Settings -> Add Logger) and saving, but there's something else at play as I can now add new log level settings without reproducing.

Environment

• Payara Version: 4.1.2.172
• Edition: Full
• JDK Version: 8
• Operating System: Mac
• Database: MySql

[mikecroft]

Hi @zfarrell thanks for raising this! You'll be pleased to know this has already been found, fixed and merged! The first issue to raise it was #1680 and the cause was that the admin console did not support the ALL logger level, which was brought in by an upstream change GLASSFISH-21560.

The fix has been merged in #1691 so we expect it to be released in Payara Server 173 next month.

[zfarrell]

Great to hear, thanks for the quick response (and fix ;) )!