]
James Perkins updated LOGMGR-263:
---------------------------------
Fix Version/s: 2.1.15.Final
2.2.0.Final
3.0.0.Final
Logger Lookup is much slower as with JDK 8
------------------------------------------
Key: LOGMGR-263
URL:
https://issues.redhat.com/browse/LOGMGR-263
Project: JBoss Log Manager
Issue Type: Bug
Environment: WildFly 17, OpenJDK 11
Reporter: Andreas Liebscher
Assignee: James Perkins
Priority: Critical
Fix For: 2.1.15.Final, 2.2.0.Final, 3.0.0.Final
Attachments: ClassInEar.java, LogContextCacher.java, getlogger-stack.txt,
grafik1570016303722 (1).png, grafik1570016303722.png, grafik1570016791285.png,
logger-demo.war, responsetimes.png
During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK
11 we had a serious performance issue. We identified the usage of the logging framework
SLF4J with the pattern `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason
when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to
some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8
got a performance improvement with the added `static` keyword.
Please check the VisualVM output as prove of JDKSpecific got slower: