PI26813: WHEN E.PRINTSTACKTRACE() IS CALLED, THE OUTPUT CAN BE MISSING SOME LINES OF USER CODE

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The Liberty profile will trim frames relating to server
  internals from printed stack traces in the console.log and
  messages.log files. (The trace.log will always have completed
  stack traces.)
  .
  If a stack trace is printed using e.printStackTrace() (rather
  than passed as a parameter in a logging call), the server would
  trim all frames below the first internal method. This means that
  if there is a callback from Liberty code or third party code to
  user code, the user code would not be printed.
  .
  This fix ensures that all user code and third party code is
  included in printed stack traces.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When e.printStackTrace() is called, the *
  *                      trimmed console output may be missing   *
  *                      some lines of user code                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a stack trace is printed using e.printStackTrace() (rather
  than passed as a parameter in a logging call), the server will
  trim all frames below the first internal method. This means that
  if there is a callback from Liberty profile code or third party
  code to user code, the user code would not be printed.
  

Problem conclusion

• Trimming of stack traces has been updated to ensure callbacks to
  user code are always included.
  
  The fix for this APAR is
  currently targeted for inclusion in fix pack 8.5.5.4.  Please
  refer to the Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• The trace.log file will always have complete stack traces. If
  exceptions are passed as a parameter in a log call, the stack
  trace will always be trimmed without removing any user code.
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP