-
Bug
-
Resolution: Done
-
Major
-
None
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:
- clones
-
LOGMGR-263 Logger Lookup is much slower as with JDK 8
- Resolved
- is cloned by
-
JBEAP-18947 [GSS](7.2.z) LOGMGR-263 - Logger Lookup is much slower as with JDK 8
- Closed
- is incorporated by
-
JBEAP-19269 [GSS](7.3.z) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final
- Closed
- relates to
-
JBEAP-19276 [GSS](7.3.z) WFCORE-4860 - Performance degradation with the LogContextSelector on Java 11
- Closed