To return expected results, you can:

  • Reduce the number of search terms. Each term you use focuses the search further.
  • Check your spelling. A single misspelled or incorrectly typed term can change your result.
  • Try substituting synonyms for your original terms. For example, instead of searching for "java classes", try "java training"
  • Did you search for an IBM acquired or sold product ? If so, follow the appropriate link below to find the content you need.
  • Custom 503 messages received from WebSphere Application Server
    are not passed to client.
    The WebSphere Application server plugin component would use
    the default 503 message instead of passing the custom message
    back to client.
    Plugin Trace:
    [Thu Jun 12 22:52:46 2008] 0005a0e0 00000001 - TRACE:
    HTTP/1.1 503 Service Unavailable
    [Thu Jun 12 22:52:46 2008] 0005a0e0 00000001 - ERROR:
    lib_htresponse: htresponseRead: Response code 503 received;
    retrying
    [Thu Jun 12 22:52:46 2008] 0005a0e0 00000001 - ERROR: ws_common:
    websphereExecute: Failed to read from a new stream; App Server
    may have gone down during read
    The IP trace between plug-in and the application server showed
    the application server did send the headers.
    

    Local fix

    Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server plugin component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Custom 503 messages received from       *
    *                      WebSphere Application Server are not    *
    *                      passed to client                        *
    ****************************************************************
    * RECOMMENDATION:  This fix superceds PK68126.                 *
    ****************************************************************
    The WebSphere Application server plugin component would use
    the default 503 message instead of passing the custom message
    back to client.
    

    Problem conclusion

  • The plugin component will retry another server when it
    receives a 503 message but if the last server attempted sends
    a custom 503 message, it will be passed back to the client.
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.0.2.35, 6.1.0.27, 7.0.0.5.  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

    PK84396

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-08

  • Closed date

    2009-05-15

  • Last modified date

    2009-10-27

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

  • [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
  •