PM90084: TRACE STRING OPTIMIZATION RESULTS IN INCORRECT TRACE SPECIFICATION WHEN SPECIFIED IN CONFIGURATION TAB

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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

APAR status

• Closed as program error.

Error description

• The issue is related to the following trace string:
  *=info: com.dwl.*=warning: com.ibm.mdm.*=warning:
  com.ibm.mdm.server.config.*=info
  
  If the above trace specification is put in the "Runtime" tab,
  using the WebSphere Administrative Console, it is honored as
  written.
  
  However, if the same trace specification is put in the
  "Configuration" tab, or if it "Saved to configuration" from the
  "Runtime" tab, it is changed to the following:
  *=info: com.dwl.*=warning: com.ibm.mdm.*=warning
  
  These are not equivalent trace specifications.
  

Local fix

• The client can manually edit the trace string in the server.xml
  file to "back-off" the optimization that is done when the
  string is saved to the file via the AdminConsole code.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5.5                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Trace specification was not getting     *
  *                      optimized correctly in the              *
  *                      Configuration Tab.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a trace is applied in the configuration tab and the server
  is restarted the trace string is not correctly optimized.
  

Problem conclusion

• A suitable message is now displayed in the logs which conveys
  that the trace string is optimized.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP