PI21485: STACKOVERFLOWERROR OR INFINITE LOOP USING HPEL LOGGING

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

• On Liberty 8.5.5.2, enabling hpel logging (e.g. by including
  "websphere.log.provider=binaryLogging-1.0" in
  bootstrap.properties and
  using a trace filter including com.ibm.ws.adaptable.module or
  archive.adaptable (such as by setting "*=all"  will result in an
  infinite loop shown by an FFDC with a StackOerflowError with
  stack trace
  looping through
   at
  com.ibm.ws.adaptable.module.internal.AdaptableContainerImpl.getE
  ntry(Ada
  ptableContainerImpl.java:113)
  

Local fix

• Disable HPEL logging
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: StackOverFlow exception due to infinite *
  *                      loop when using HPEL logging            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Users who are using the High Performance Extensible Logging
  (HPEL) feature and have their trace specification set to
  com.ibm.ws.logging.trace.specification=*=all
  may face a
  StackOverFlow exception.
  

Problem conclusion

• To avoid the infinite loop situation, we have restructured our
  HPEL code. The current HPEL logging is now in sync with
  traditional text logging.
  
  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

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