PI27210: DEPLOYMENT OF A LARGE APPLICATION WITH VERY DETAILED TRACE ENABL ED MAY CAUSE A TRACING LOOP

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

• APAR for defect 100634 and defect 106890.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile with very detailed   *
  *                  trace enabled                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Deployment of a large application with  *
  *                      very detailed trace enabled may cause a *
  *                      tracing loop                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using very detailed trace, for example "*=all=enabled", a
  tracing loop in ZipFileEntry is possible.
  
  The repeated log will
  look like:
  
  [WARNING ] CWWKC0004W: [
  ClassSourceImpl_MappedContainer@-1527753085(WEB-INF/lib/db2.jar,
  com.ibm.ws.adaptable.module.internal.InterpretedContainerImpl@98
  c58c6c) ]: The conversion of [md.class] as
  [com.ibm.ws.adaptable.module.internal.InterpretedEntryImpl@ed707
  785] under root
  [com.ibm.ws.adaptable.module.internal.InterpretedContainerImpl@7
  4904113] for prefix [com/ibm/db2/jcc/am] failed.
  

Problem conclusion

• Tracing was restricted during the relevant ZipFileEntry steps to
  prevent log looping.
  
  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

• Avoid usingtrace specifications like "*=all=enabled."
  

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