IBM Support

PM85434: WEB 2.0 WEB MESSAGING EXCEEDS TCP CONNECTION LIMIT

Fixes are available

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using Web 2.0 web messaging function you could see messages
    from the channel framework that the number of connections for a
    port exceeds the defined connection limit.  Like:
    
    [3/20/13 10:47:27:088 EDT] 00001439 TCPChannel    W   TCPC0004W:
    TCP Channel TCP_2 has exceeded the maximum number of open
    connections 20000.
    
    Also seen...
    
    [3/19/13 14:06:34:761 EDT] 00000088 PassThroughCo W
    CWPSB1025E: The Web messaging channel caught the following
    unexpected exception during an asynchronous read operation:
    java.net.SocketTimeoutException:
    Async operation timed out
     at
    com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.
    futureCompleted(AioReadCompletionListener.java:139)
     at
    com.ibm.io.async.AbstractAsyncFuture.invokeCallback(
    AbstractAsyncFuture.java:217)
     at
    com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.
    java:205)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613)
    Caused by: com.ibm.io.async.AsyncTimeoutException(Async
    operation timed out, [Timeout, rc=0])
     at
    com.ibm.io.async.AsyncSocketChannelHelper$tCallback.
    timerTriggered(AsyncSocketChannelHelper.java:109)
     at com.ibm.io.async.Timer.checkForTimeouts(Timer.java:426)
     at com.ibm.io.async.Timer.run(Timer.java:241)
    
    [3/19/13 14:06:36:316 EDT] 00000905 BayeuxClientM W
    CWPSB1314W: Bayeux error 401 occurred when processing a Bayeux
    request for channel / with arguments h2c8zz899gSbpC5C8KnuizG in
    Web messaging definition events.war_WebMsgServlet.
    [3/19/13 14:06:36:813 EDT] 000010a8 PassThroughCo W
    CWPSB1025E: The Web messaging channel caught the following
    unexpected exception during an asynchronous read operation:
    java.net.SocketTimeoutException: Async operation timed out
     at
    com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.
    futureCompleted(AioReadCompletionListener.java:139)
     at
    com.ibm.io.async.AbstractAsyncFuture.invokeCallback(
    AbstractAsyncFuture.java:217)
     at
    com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.
    java:205)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613)
    Caused by: com.ibm.io.async.AsyncTimeoutException(Async
    operation timed out, [Timeout, rc=0])
     at
    com.ibm.io.async.AsyncSocketChannelHelper$tCallback.
    timerTriggered(AsyncSocketChannelHelper.java:109)
     at com.ibm.io.async.Timer.checkForTimeouts(Timer.java:426)
     at com.ibm.io.async.Timer.run(Timer.java:241)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the Web Messaging service      *
    *                  feature.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running a Web messaging enabled    *
    *                      application, TCP MaxConnections can be  *
    *                      exceeded which halts app server web     *
    *                      traffic.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running a Web messaging enabled application, TCP
    MaxConnections can be exceeded due to an incorrect cleanup
    mechanism when a TCP error is encountered.  This error should
    not occur during normal Web messaging operations, but a poorly
    behaving proxy or load balancer could trigger the problem.
    

Problem conclusion

  • The problem has been fixed.  The Web messaging code is
    correctly cleaning up the TCP connection when encountering an
    error condition.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.31, 8.0.0.8, and 8.5.5.1.  Please refer to the
    Recommended Updatespage for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM85434

  • 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

    2013-03-22

  • Closed date

    2013-08-06

  • Last modified date

    2013-08-06

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM85434

Modified date: 06 August 2013