Changes in GlassFish 7 Logging System

For GlassFish 7 we completely changed the logging system (GJULE = GlassFish Java Util Logging Extension), fixed many bugs, improved performance and its reliability. This long boring video will show you what happened - and also what you should and should not do when you need useful logs.

0:00 Introduction
1:11 Basics - Logger
3:56 Basics - Handler
6:33 Basics - Formatter
7:20 Basics - LogManager and basic rules
11:17 How logging starts in GlassFish
13:17 GlassFish Handlers
15:38 GlassFish Formatters
17:50 Start of GlassFish and an intruder in server.log
19:26 Start without --verbose, ODL vs. Uniform
20:36 Using logs in automatic tests
23:21 Test Coverage of GJULE, Code Quality
26:23 Conventions: Why we removed HK2 from logging
30:46 Fixed Issues
31:17 Live - starting GF 7.0.3 with FINEST level (I am talking about GF6 for a while, sorry)
36:03 Live - logging of the asadmin stop-domain
38:12 Live - logging of the asadmin start-domain and slow AdminUI deployment
38:42 Live - GF6: milliseconds, GF7: microseconds
40:01 Effectivity - When to resolve Log Messages? Good side effects!
43:56 Live - GF6 issues, especially failure to start with FINEST
48:40 Performance vs. Responsibilities of threads
49:27 Logging of Logging
50:57 Logging Antipatterns
56:16 Virtualization of the year 2000.

Notes:
Original JSR-47 of 1999: https://www.jcp.org/en/jsr/detail?id=47
What I said about "Log Domain Standard" is rather my speculation, I don't know that.
External implementations I could not remember - SLF4J, Logback, Log4J2, ...

You can sponsor us on https://github.com/sponsors/OmniFish-EE or you can take a look on our web site and buy our services https://omnifish.ee/solutions/ - especially we can help you with the migration to GlassFish 7 + Java 17 from any Jakarta EE/Java EE implementation.