Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.3.2.CR1, 7.3.2.GA
Affects Version/s: None
Component/s: Logging
Labels:
- downstream_dependency

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Target Release:

7.3.z.GA
Git Pull Request:
https://github.com/jboss-logging/jboss-logmanager/pull/295

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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

Assignee:: Ilia Vassilev

Reporter:: Ilia Vassilev

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2020/04/17 8:07 AM

Updated:: 2024/08/27 1:57 PM

Resolved:: 2020/04/17 8:47 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates