PH17812: INTELLIGENT MANAGEMENT WEB SERVER PLUGIN 9.0.5.1 CRASHES IF AN INVALID TRACE SPECIFICATION IS DEFINED

9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• Intelligent Management Web server Plugin 9.0.5.1 crashes
  during initialization if an invalid trace specification has
  been defined. Examples: http.reques:DEBUG *:ERROR Crash
  stack: libodr!trContextSetSpec libodr!odrRuleSetPropStr
  libodr!jsonHandleObjects libodr!jsonHandleObjects
  libodr!jsonHandleObjects libodr!jsonHandleObjects
  libodr!jsonHandleObjects libodr!jsonHandleObjects
  libodr!jsonHandleObjects libodr!jsonHandleObjects
  libodr!jsonHandleObjects libodr!jsonHandleObjects
  libodr!jsonHandleOp libodr!jsonHandle
  libodr!odrRoutingInfoPopulate
  libodr!odrCreateAndPopulateNewRoutingInfo
  libodr!odrResetRoutingInfo libodr!odrHandleJson
  libodr!odrHandleJsonFromRestService
  libodr!odrRestResponseHandler2 libodr!odrRestResponseHandler
  mod_was_ap24_http!ws_ReallySendRequest Problem first
  observed in Plugin 9.0.0.11. Crash does not occur in Plugin
  9.0.0.10 and earlier.
  

Local fix

• correct IM trace spec
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server WAS ND edition- Virtual              *
  *                  Enterprise/IM Component                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Intelligent Management Web Server       *
  *                      Plugin may crash with some invalid      *
  *                      forms of trace specification            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some instances, when an invalid format of trace specification
  is specified for the Intelligent Management Web Server Plugin,
  the Plugin will crash, causing it to recycle repeatedly.  An
  example of an invalid trace specification would be ?*:DEBUG?.
  The expected format is ?:DEBUG?.
  

Problem conclusion

• The Intelligent Management Web Server Plugin was altered to
  better handle an invalid trace specification and fail more
  gracefully.  In the event an invalid trace specification is
  provided, an ODR:ERROR message is created as follows: ODR:ERROR:
  Internal error.  Details: '*:DEBUG'.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 9.0.5.3.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• If the user provides a trace specification using expected
  syntax, the problem will not occur.
  

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

• R900 PSY

     UP