IBM Support

PM21892: SERVER STOPS RESPONDING TO REQUESTS AFTER MAKING AN OUTBOUND JAX-RPC CALL.

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server stops responding to
    requests after making a JAX-RPC call to a Web Service
    application.  These messages appears in trace.log when
    webservices tracing is enabled:
    
    [8/31/10 16:05:58:584 EDT]
    00000033 WSChannelMana 1   WSWS3505I:
    Creating channel named: httpclient-tcp-outbound
    [8/31/10 16:05:58:585 EDT] 00000033 WSChannelMana 3
    WSWS3228E: Error:
    Exception: com.ibm.ws.tcp.channel.impl.ZAioTCPChannelFactory
    [8/31/10 16:05:58:585 EDT] 00000033 WSChannelMana 3   Using:
    class
    com.ibm.ws.tcp.channel.impl.TCPChannelFactory
    .
    .---------------------------------------------------
       The problem documented in this APAR can also effect HAManager
    processing.  This is not a common symptom of this problem, but
    it can be a side-effect of it, since the problem in this APAR
    can make the TCP channel that is used by both HAManager and
    WebServices be tied up.  The HAManager messages that might occur
    as a result of this issue are these.
    .
       There may be numerous occurrences of
    [3/6/11 0:13:27:604 EST] 0000001b MbuRmmAdapter W   DCSV1115W:
    DCS Stack DefaultCoreGroup at Member B2DA\B2DA5\DCS02_CM5:
    Member B2DA\B2DA2\DCS02_CM2 connection  was closed. Member will
    be removed from view. DCS connection status is View|Gossip,
    this member is suspected by the other member.
    .
    [3/6/11 19:59:19:401 EST] 00000020 DiscoveryRcv  W   DCSV1112W:
    DCS Stack DefaultCoreGroup at Member B2DA\B2DA6\DCS07_CM6:
    Member B2DA\B2DA7\nodeagent failed to respond to periodic
    heartbeats.
    Member will be removed from view. Configured Timeout is 360000
    milliseconds.  DCS logical channel is Discovery|Ptp.
    .
    and possibly even
    DCSV9416E: An internal error occurred. Exception is
                   com.ibm.ws.dcs.common.exception.
                   DCSTransportLayerException:
    CheckConnectionPending
    at
    com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.common.LogAdapter.
        handle9416
    

Local fix

  • This problem does not happen when switching webservices call
    from JAX-RPC to Axis.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7 users of*
    *                  JAX-RPC Web services clients.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Server stops responding to requests     *
    *                      after making an outbound JAX-RPC call.  *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR.    *
    ****************************************************************
    A Web services application stops responding to requests after
    making an outbound JAX-RPC call.  Following messages appears
    in trace.log when webservices tracing is enabled:
    
    [8/31/10 16:05:58:584 EDT]
    00000033 WSChannelMana 1   WSWS3505I:
    Creating channel named: httpclient-tcp-outbound
    [8/31/10 16:05:58:585 EDT] 00000033 WSChannelMana 3
    WSWS3228E: Error:
    Exception: com.ibm.ws.tcp.channel.impl.ZAioTCPChannelFactory
    [8/31/10 16:05:58:585 EDT] 00000033 WSChannelMana 3   Using:
    class
    com.ibm.ws.tcp.channel.impl.TCPChannelFactory
    
    Customer may see following error when Channel Framework trace
    is enabled:
    
    [8/31/10 16:08:58:572 EDT] 0000003f TCPChannelFac >   destroy
    Entry
    [8/31/10 16:08:58:572 EDT] 0000003f AioTCPChannel >  terminate
    Entry
    [8/31/10 16:08:58:572 EDT] 0000003f AioTCPChannel 3
    terminate - call AsyncLibrary.shutdown
    ... ...
    [8/31/10 16:10:46:261 EDT] 00000006 ChannelSelect 3
    Unexpected Exception Caught in ChannelSelector.run
    java.lang.RuntimeException:
    java.lang.Throwable: Library not initialized
    

Problem conclusion

  • When running in a server environment, the JAX-RPC runtime was
    using the incorrect channel factory to create the outbound
    channel chain. This error leads to the Channel Framework
    stopping/unloading the TCP Channel when this channel chain
    stops.  The JAX-RPC runtime has been updated to use the
    correct channel factory.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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

    PM21892

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-03

  • Closed date

    2010-09-16

  • Last modified date

    2011-03-16

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM21892

Modified date: 16 March 2011