PH11759: PERFORMANCE DROPS WHEN WRITING A LARGE AMOUNT OF LOG ENTRIES TO LIBERTY'S CONSOLE LOG

19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

APAR status

• Closed as program error.

Error description

• When application log entry is sent to Liberty console logger
  (
  for example, by using logback's ConsoleAppender ),
  Liberty will perform extra formatting ( by adding timestamp,
  thread ID, class name, etc ) before writing to messages.log
  
  These extra overhead can cause performance degradation when
  there is a large volume of log entries to be processed.
  

Local fix

• Avoid using ConsoleAppender as the main logging mechanism
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Customer reporting lower than expected  *
  *                      TPS when using SystemOut for logging    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There are some inferring calls in the code such as
  LogRecord.getSourceClassName() and
  LogRecord.getSourceMethodName() that are expensive to execute
  and hence slow down the performance for SystemOut.
  

Problem conclusion

• LogRecord.getSourceClassName() and
  LogRecord.getSourceMethodName() calls were removed from the
  logging call stacks. As a result, we are seeing a siginificant
  boost in logging performance on SystemOut.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 19.0.0.6.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• RCD0 PSY

     UP