IBM Support

PI73752: SUPPRESS FFDC FOR COM.IBM.IO.ASYNC.ASYNCSOCKETCHANNEL 453

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the case where the Liberty Server uses Async I/O, as seen
    by
    message:
    CWWKB0103I: Authorized service group ZOSAIO is available.
    
    And a client opens a SSL connection where the SSL handshake
    completes but no request is sent on the connection, and then
    the connection is closed, the Liberty server will cut this
    FFDC
    in the log:
    
    FFDC1015I: An FFDC Incident has been created:
    "java.io.IOException: Async IO operation failed, internal
    error
    com.ibm.io.async.AsyncSocketChannel 453"
    
    FFDC file contains:
    Exception = java.io.IOException
    Source = com.ibm.io.async.AsyncSocketChannel
    probeid = 453
    Stack Dump = java.io.IOException: Async IO operation failed,
    internal error
    at com.ibm.io.async.AbstractAsyncChannel.multiIO
    (AbstractAsyncChannel.java:474)
    at com.ibm.io.async.AsyncSocketChannelHelper.read
    (AsyncSocketChannelHelper.java:243)
    at com.ibm.io.async.AsyncSocketChannelHelper.read
    (AsyncSocketChannelHelper.java:350)
    at com.ibm.ws.tcpchannel.internal.AioSocketIOChannel.
    readAIO(AioSocketIOChannel.java:124)
    at
    com.ibm.ws.tcpchannel.internal.AioTCPReadRequestContextImpl.
    processAsyncReadRequest(AioTCPReadRequestContextImpl.java:79
    )
    at com.ibm.ws.tcpchannel.internal.TCPReadRequestContextImpl.
    readInternal(TCPReadRequestContextImpl.java:166)
    at com.ibm.ws.tcpchannel.internal.TCPReadRequestContextImpl.
    read(TCPReadRequestContextImpl.java:137)
    at com.ibm.ws.channel.ssl.internal.SSLReadServiceContext.
    read(SSLReadServiceContext.java:494)
    at com.ibm.ws.channel.ssl.internal.SSLReadServiceContext.
    read(SSLReadServiceContext.java:377)
    at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.
    readyInboundPostHandshake(SSLConnectionLink.java:701)
    at com.ibm.ws.channel.ssl.internal.
    SSLConnectionLink$MyHandshakeCompletedCallback.complete
    (SSLConnectionLink.java:391)
    at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake
    (SSLUtils.java:976)
    at com.ibm.ws.channel.ssl.internal.SSLHandshakeIOCallback.
    complete(SSLHandshakeIOCallback.java:88)
    at com.ibm.ws.tcpchannel.internal.AioReadCompletionListener.
    futureCompleted(AioReadCompletionListener.java:157)
    at com.ibm.io.async.AbstractAsyncFuture$WorkCallback.
    run(AbstractAsyncFuture.java:385)
    at java.util.concurrent.ThreadPoolExecutor.runWorker
    (ThreadPoolExecutor.java:1157)
    at java.util.concurrent.ThreadPoolExecutor$Worker.
    run(ThreadPoolExecutor.java:627)
    at java.lang.Thread.run(Thread.java:798)
    

Local fix

  • Disable Async I/O with
    com.ibm.ws.tcpchannel.useZosAio=false
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC incident for Async I/O read        *
    *                      complete with 0 bytes on z/OS           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A server running Asynchronous TCP/IP Sockets I/O for Liberty on
    z/OS (asyncIO) may observe FFDC Incidents related to read
    requests
    receiving 0 bytes read.
    
    A client started connection was closed without sending any data.
    This
    resulted in TCP/IP completing a synchronous server read request
    immediately
    with an indication of 0 bytes read.
    
    The asyncIO java code created the following FFDC, before
    throwing an
    IOException to cleanup the server-side of the connection.  This
    FFDC is
    not needed as this is a "normal" scenario.
    
    FFDC1015I: An FFDC Incident has been created:
    "java.io.IOException:
    Async IO operation failed, internal error
    com.ibm.io.async.AsyncSocketChannel 453"
    

Problem conclusion

  • Code has been modified to remove the creation of an FFDC
    Incident
    when receiving 0 bytes on a read request that completes
    immediately.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.1.  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

    PI73752

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-14

  • Closed date

    2017-01-25

  • Last modified date

    2017-01-25

  • 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

    LIBERTY PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"CD0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2020