IBM Support

PI25570: 500 ERROR WHEN BUILDING AN EXPRESSION IN THE SUBEXPRESSION BUILDER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This error happens in On Demand Router --> On Demand Router
    Properties -->Routing policy HTTP rules -->SubExpressionBuilder.
    
    After setting given rule : If port <> 443 and uri LIKEIN
    ('/payment','/payment/%')
    Then Reject routing with error code 404
    
    When trying to add another condition and select "Select
    Operand" to protocol, the following error is thrown:
    
    "Error 500
    An error occurred while processing request:
    /ibm/console/RulesCollection.do
    Message: java.lang.IllegalArgumentException"
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Special Characters in Subexpression     *
    *                      Builder cause 500 Error in              *
    *                      RulesCollection.do and generate         *
    *                      IllegalArgumentException                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This error happens in On Demand Router --> On Demand Router
    Properties --> Routing policy HTTP rules -->
    SubExpressionBuilder.
    When using the SubExpressionBuilder, routing polcy rules
    that contain special characters cause the server to
    generate Error 500 in the RulseCollection.do file. The Java
    Message report given is java.lang.IllegalArgumentExcpetion.
    In this case, a rule containing a % sign would properly
    validate and appear to be saved. When a user
    attempts to append a new rule to this existing rule set,
    however, the request would fail.
    

Problem conclusion

  • Debugging revealed a code defect where several URLs were not
    being properly encoded. This update includes the encoding fixes
    that make it possible to include special characters as part of
    HTTP routing rules.
    
    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 number

    PI25570

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-09-11

  • Closed date

    2014-10-10

  • Last modified date

    2014-10-10

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022