IBM Support

PM46270: WHEN USING MVS LOGSTREAMS FOR WEBSPHERE APP SERVER ERROR LOGS SERVANT MAY CONNECT TO LOGSTREAM MULTIPLE TIMES AND USE HIGH SQA

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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.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
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
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When WebSphere Application Server is configured to use the z/OS
    Logstream for recording of it's 'error log' information, it
    uses the z/OS Logger utility.
    The WebSphere Application Servant region Address Space will
    connect to the Logstream (IXGCONN) and then Write (IXGWRITE) to
    the Logstream.
    Logger limits the number of writes that any one connection can
    have in it's 'write queue'.  Each of the 'queued writes' is
    backed by SQA Storage in the z/OS System.
    It has been found that the WebSphere Servant Regions may
    'connect' multiple times.  If Logger is not able to process the
    'Writes' that are queued to it, SQA Storage will be used to hold
    the SRB';s associated with the queued messages.
    Depending on system configuration and availability of common
    storage on the system, this queue of SRB's may cause an SQA
    Storage Shortage on the System.
    
    This apar will also change the handling of some error/warning
    codes that are returned from Logger. For example when
    RC=00000004, RSN=00000407 is returned, WebSphere will log a
    message that there has been a possible loss of data, but it will
    continue writing to the logstream instead of current design of
    disconnecting from the logstream and sending the messages to
    CERR instead.
    

Local fix

  • If it is determined that an SQA Storage shortage is caused by
    Logger queue of SRB's from the WebSphere Servant Region Address
    Space, then the WebSphere configuration can be changed to not
    use Logstream for it's 'error log'
    The WebSphere variable that is set to point to a Logstream is:
        ras_log_logstreamName
    If this is set to point to a Logstream dataset name, you can
    simply remove this variable, and re-start the WebSphere Server
    to pick up the change.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1.0 and V8.0.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      makes multiple concurrent connections   *
    *                      to the errorlog logstream.              *
    *                      Also, WebSphere stops writing to the    *
    *                      errorlog logstream when it receives a   *
    *                      IXGCONN RC=00000004 and RSN=00000407.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere errorlog logstream (ras_log_logstreamName)
    implementation does not interpret various IXGWRITE and IXGCONN
    return and reason codes correctly.
    This can lead to a WebSphere address with multiple connections
    to the logstream.   This can negate the restriction of
    outstanding IXGWRITE requests.  Exceeding the limit for
    outstanding IXGWRITE requests can exhaust system resources,
    such as storage.  ABENDS878 RC=4 was observed for a case were
    the previous condition ran the system out of SQA storage.
    Another observed scenario resulted from an incorrect handling
    of the IXGCONN RC=4, RSN=407.  In this case, WebSphere stopped
    directing messages to the logstream.  Instead the messages
    were written to the default message location (typically CERR).
    

Problem conclusion

  • Code has been modified to properly re-act to the IXGWRITE and
    IXGCONN return and reason codes.  WebSphere will properly
    recognize when our logstream connection has been lost and only
    then re-connect based on the IXG reason codes.
    
    APAR PM46270 is currently targeted for inclusion in Service
    Level (Fix Pack) 6.0.0.43 of WebSphere Application Server V6.1.0
    and Fix Pack 8.0.0.2 of WebSphere Application Server V8.0.
    
    The fix will also be delivered as sysrouted APAR PM49734 in
    WebSphere Application Server V7.0 for z/OS.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM46270

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-23

  • Closed date

    2011-10-11

  • Last modified date

    2012-04-03

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

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

    PM49734

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R610 PSY UK76696

       UP12/03/18 P F203

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 6.1

Reference #: PM46270

Modified date: 03 April 2012