IBM Support

PK76785: CORRUPTED IIOP MESSAGES ARE DROPPED AND CONNECTION FAILED, CAUSING IIOP MESSAGE ORIGINATOR TO TIME OUT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IIOP messages arrive at the WebSphere Application Server
    controller region IIOP port, but there are 4 extra bytes at
    the beginning of the message. When this happens, the message
    fails basic syntax checking because all IIOP messages begin with
    the ascii string "GIOP". Such corrupted messages are discarded
    and the connection is failed. The process which sent the IIOP
    request is not notified of the failure. No response is
    generated, and eventually the sender times out, usually
    resulting in an SEC3 ABEND.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  V7.0 for z/OS                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: The WebSphere Application Server for    *
    *                      z/OS server fails to respond to an      *
    *                      IIOP client's GIOP request when the     *
    *                      GIOP message header is malformed,       *
    *                      causing the IIOP client to hang.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the WebSphere Application Server for z/OS server receives
    a GIOP message with a malformed message header, the server
    reports the exception with an FFDC record but does not respond
    to the IIOP client with an exception.  Thus, the client
    receives no indication from the server that the server failed
    to process the GIOP message.  The client waits indefinitely for
    a response that will never be sent.
    

Problem conclusion

  • Updated the server code to terminate the IIOP connection when a
    malformed GIOP message header is encountered, thus alerting the
    IIOP client that the server could not process the GIOP
    message.
    
    APAR PK76785 is currently targeted for inclusion in
    Service Level 7.0.0.3 of WebSphere
    Application Server  for z/OS.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK76785

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-03

  • Closed date

    2009-03-19

  • Last modified date

    2009-05-03

  • APAR is sysrouted FROM one or more of the following:

    PK75990

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK45120

       UP09/04/06 P F904

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
10 February 2022