IBM Support

IJ24641: MAXIMO DOES NOT LOG A 503 ERROR STATUS CODE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • ERROR DESCRIPTION:
    Maximo does not appear to log a 503 error
    status code
    
    PROBLEM DESCRIPTION:
    While troubleshooting session
    growth / stranding in maxsession we have identified what
    appears to be a defect in the way 503 status codes are returned
    by Maximo's webcontainer. Maximo does not appear to send a
    status code of 503 when a capacity related error occurs
    (instead sending a standard page with the error and a status
    200). I believe it should send the error with a status code 503
    to allow for the IHS plugin to either mark the server down or
    send the request to another JVM.
    
    For example:
    
    When uisessions
    climb >=2 and:
    
    mxe.webclient.maxuisessions=2
    mxe.webclient.maxu
    isessionsend503=1
    
    Maximo returns an error page showing text of
    "The maximum number of users are logged in. Try again later
    after some users have logged off.".
    
    The status of this page is
    200, not 503. This means the JVM cannot be marked down or
    redirect requests to an alternate JVM
    
    PERFORMANCE ISSUE:
    
    No
    
    
    ENVIRONMENT:
    App Server IBM WebSphere Application Server
    8.5.5.16
    
    Version
    
    Tivoli's process automation engine
    7.6.1.0-IFIX20200302-1500 Build 20180718-1141 DB Build V7610-83
    HFDB Build HF7610-13
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MAXIMO DOES NOT LOG A 503 ERROR STATUS CODE                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • FIXED IN webClientRuntime.java
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ24641

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-29

  • Closed date

    2020-09-18

  • Last modified date

    2020-09-18

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
19 September 2020