IBM Support

PI53803: IPLANET STATIC CONTENTS RETURNED '503' STATUS CODE WHEN IT HAS PLUG-IN CONFIGURED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment: WebSphere plug-in for Oracle iPlanet web server on
    a Solaris machine.
    The customer applied plug-in 8.0.0.11 and Solaris patch:
    SunOS ussbpib038amtsa 5.10 Generic_150400-28 sun4v sparc
    SUNW,SPARC-Enterprise-T5120
    
    Requests to access contents in the application server worked
    fine. However, requests to access static contents on iPlanet
    failed with HTTP '503' status code. When iPlanet plug-in
    configuration was removed, the static contents worked fine.
    
    When a request to access a static content failed, the error log
    has the following message:
    . . .  trying to GET /, func_exec reports: fn="as_handler"
    Directive="Service" returned -1 (REQ_ABORTED)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server iPlanet    *
    *                  web server plugin users                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Requests sent to iPlanet which are      *
    *                      not handled by plugin may fail          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If plugin is the first module to handle a request that it will
    not forward to WebSphere then the return code provided to the
    web server may cause further processing to stop and the client
    to receive a failure msg.
    

Problem conclusion

  • Modified the return code used by plugin when the request does
    not match plugin configuration and will not be forwarded to
    WebSphere so that the web server continues processing the
    requeset.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.41, 8.0.0.13 and 8.5.5.9.  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

    PI53803

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-09

  • Closed date

    2016-01-04

  • Last modified date

    2016-01-04

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • 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.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022