IBM Support

PI96649: PLUG-IN FAILS TO WRITE DATA WITH RC=10035 IN WINDOWS.

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

  • When data is read from the client and sent to WAS faster than
    WAS can read the data, it results in the OS telling plug-in to
    delay the writing. Once the OS indicates the socket is ready,
    the plug-in retries writing, but fails to write to WAS with
    RC=10035. Although the OS just indicated the socket is ready,
    it reports the socket is busy again.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server web        *
    *                  server plugin users                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Writes to the WebSphere Application     *
    *                      server may fail with errors that the    *
    *                      socket is busy.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the OS notifies plugin when a socket is busy and to delay
    sending data, plugin calls an OS function to wait (up to the
    serveriotimeout value) for the socket to be ready to handle
    additional data. On windows (this has only been observed with
    the IIS webserver), the OS notifies plugin that the socket is
    ready but the write attempt fails saying the socket is busy.
    

Problem conclusion

  • Plugin has added an additional write attempt when a "busy"
    failure occurs immediately after the OS has reported that the
    socket is ready. If this third write attempt fails, the
    connection will be terminated in error.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.14 and 9.0.0.8.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • An alternate solution is to perform tuning on the application
    servers so that they can receive data as fast as plugin sends
    it.
    

Comments

APAR Information

  • APAR number

    PI96649

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-12

  • Closed date

    2018-04-12

  • Last modified date

    2018-04-12

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PI96649

Modified date: 12 April 2018


Translate this page: