IBM Support

PM76420: PLUGIN MAY USE STALE SOCKETS WHEN SENDING A REQUEST TO THE APPLICATION SERVER

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.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

  • Plugin will reuse stale connections to the application server
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Plugin may use stale sockets when       *
    *                      sending a request to the application    *
    *                      server                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the plugin sends a request to the app server, it can use
    an existing socket instead of creating a new stream each time.
    Doing this reduces overhead in the plugin which keeps the
    request processing time to a minimum.  Issues have been seen
    where an old stream is used, but the request isn't fulfilled
    by the application server.  Most times, the stream has been
    closed by the application server and is no longer viable. When
    this situation occurs, the request will have to wait the time
    for ServerIOTImeOut to expire, before it will attempt a retry.
    

Problem conclusion

  • A new feature has been added to the plugin called
    ConnectionTTL.  This update will review the amount of time
    since an old stream was last used.  If it is determined to be
    too old, the plugin will cancel that stream and open a new one
    to service the request.  The plugin now has an internal
    default value of 28 seconds for ConnectionTTL.  This is based
    on the application server transport's persistent time out
    default of 30 seconds minus a reducer of 2 seconds.
    
    If you wish to fine tune this, you MUST set the reducer
    property called Plugin_PersistTimeOut_Reduction.
    NOTE-ConnectionTTL always present in the
    plugin-cfg.xml after PI74882 is applied.
    
    Setting the property within the Administrative Console:
    Click Servers > WebSphere application servers > server_name,
    next, click the "+" next to Administration within the Server
    Infrastructure section, and then click Custom properties.
    
    It should be set to a value no less than 2 seconds.
    If set to 2, you will have a new property called ConnectionTTL
    set within each of your server's transports with a value of
    PersistantTimeOut - 2.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.0.2, 8.0.0.6, and 7.0.0.29.  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

    PM76420

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-02

  • Closed date

    2013-02-20

  • Last modified date

    2019-02-07

  • 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: 7.0

Reference #: PM76420

Modified date: 07 February 2019