IBM Support

PI37409: POSSIBLE ABENDEC3 TIMEOUT IN WEBSPHERE Z/OS SERVANT REGION WHEN RUNNING AS CLIENT WITH WEBSERVICES AND JMS (SIBUS) IN SAME SR

Fixes are available

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running customer application code in WebSphere Application
    Server z/OS and the application uses WebServices and JMS getting
    messages from a Messaging Engine on a separate WebSphere
    Application Server (the Messaging Engine is running in the
    Adjunct of the other WebSphere Server).  The first Server may
    experience a hang in the Servant with a traceback similar to:
    java.lang.Object.wait(Native Method)
    java.lang.Object.wait(Object.java:167
    com.ibm.ws.sib.jfapchannel.impl.ExchangeReceiveListener.
       waitToComplete(ExchangeReceiveListener.java:227)
    com.ibm.ws.sib.jfapchannel.impl.ConversationImpl.
       exchange(ConversationImpl.java:988)
    com.ibm.ws.sib.comms.common.JFAPCommunicator.
       jfapExchange(JFAPCommunicator.java:386)
    com.ibm.ws.sib.comms.client.ClientSideConnection.
       trmHandshakeExchange(ClientSideConnection.java:501)
    .....
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Customer experiences ABENDS in the      *
    *                      SERVANT region. The network reader      *
    *                      threads will never read data received   *
    *                      over network.                           *
    ****************************************************************
    * RECOMMENDATION:  NONE                                        *
    ****************************************************************
    The servant regions in z/OS environment experiences ABEND due
    to
    TCP reader threads not being able to read data that is received
    over network. The TCP reader threads exit due to the way it is
    being used to create transport channels and  transport chains.
    As a result of which, the data which is arrived over the
    network
    left unread. The SIB threads indefinitely wait for the channel
    framework threads to provide this data. Because TCP READER
    threads are not available the data is never passed on. The
    problem occurs in z/OS environments when both SIB and
    WebService
    components are used heavily.
    

Problem conclusion

  • It is found that in z/OS environments the use of
    ZAioTcpChannelFactory to create channels in the servant regions
    is not allowed. The SIB code is modified to use the right
    connection factory which is WSTCPChannelFactory instead of
    using
    ZAioTcpChannelFactory. This has been identified as the cause of
    As part of this APAR code changes, the SIB code is
    modified to use WSTCPChannelFactory to create channels for
    BasicBootStrapMessaging Chain.
    
    This change is controlled by a WebSphere Application Server
    environment variable, SIB_Override_Channels_In_ZOSServant.
    This environment variable needs to be set at the cell scope to
    the value "true" or "TRUE" to enable the change introduced by
    the APAR.
    
    
    APAR PI37409 is currently targeted for inclusion in Fix Pack
    8.5.5.8 of WebSphere Application Server V8.5.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37409

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-19

  • Closed date

    2015-09-09

  • Last modified date

    2018-03-07

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

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

    PI87876 PI94825

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021