IBM Support

PI76949: The 'IN' operator of Intelligent Management: HTTP operands does not work

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The manageODR.py script can be used for ODR custom logging.
    When the user specifies "response.code = 200" for the
    'condition' argument of insertCustomLogRule, the log has
    expected output. However, when the user specifies
    "response.code IN (200,302,304)" for the 'condition'
    argument
    of insertCustomLogRule, nothing was logged in the log file.
    
    It appears the 'IN' operator does not work.
    

Local fix

  • Use 'OR' operator. For example:
    "response.code=200 OR response.code=302 OR response.code=304"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Intelligent Management               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Creating a custom logging rule for http *
    *                      response codes fails when using the IN  *
    *                      operator                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When attempting to establish a custom logging rule in the Java
    ODR, a user might wish to create one for multiple http response
    codes. For example, the rule 'response.code IN (200, 302, 304)'
    should validate correctly and log only those requests which
    contain a response code in the listed values. However, this rule
    fails to pass validation in the java ODR, and does not get
    honored. The user would observe the custom logging file get
    created and would not observe any log messages being appended to
    the file.
    

Problem conclusion

  • A code defect was identified that caused arguments in a list
    following the IN operator to fail while attempting to parse
    rules where IN contained multiple integer operators. Custom
    logging rules should now work as expected in the Java ODR.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.12.  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 number

    PI76949

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-21

  • Closed date

    2017-03-22

  • Last modified date

    2017-03-22

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021