IBM Support

PI06958: Unexpected servant data in the BBOO0327I message and possible servant termination after a WLM queue percent timer expires

Fixes are available

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.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
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A server that processes MDB Plan "A" workload is configured￴
    with the following settings:
        control_region_mdb_queue_timeout_percent: 10.
        control_region_mdb_request_timeout: 55.
    .
    During a period of heavy inbound MDB work, the server starts to
    get behind and several MDB requests reach the MDB Queue Timeout
    Percent age of 5.5 seconds. , BBOO00327I messages are issued
    for these MDBs as part of timeout processing. One of these
    requests was allowed to stay on the work queue for 1.0 seconds
    longer than it should - and it was even permitted to be
    dispatched into a servant region. However, this MDB was timed
    out almost immediately after being dispatched.
    *
    13:40:37.96
     BBOO0327I MDB Plan "A" REQUEST TIMEOUT:
              (0078):(FFFFF951):(0002000D):(009C75E0):(STC00117):
              (2013/11/12 13:40:31.484940):
              (2013/11/12 13:40:31.486188):
              (2013/11/12 13:40:37.958513):
              (mdbclass):(mdbrequest):(Local to this Server):
              ():():(InternalRequestQueue_B01Lp)
            .
    13:40:38.06
     BBOO0232W A request for Class Name 'mdbclass' and Method Name
              'mdbrequest', from Local to this Server, has timed
              out.  The servant process associated with the request
              will be terminated. Request Id(FFFFF951)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      Servant process is terminated after a   *
    *                      WLM Queue percent timer expired.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A WLM queue percent timer recovers a request which exceeds a
    specified time spent on the WLM queue prior to being selected
    for execution by a Servant.
    A small window exists where a request is considered still
    on the WLM queue and has triggered the WLM Queue percent
    cleanup, but the request is allowed to progress to its next
    state.  This progression in request state may cause a common
    cleanup routine to decide to terminate the associated Servant
    for the request.
    The result is that a request which would have been allowed
    to run its full dispatch timeout value was only given its WLM
    queue percent value before the Servant was terminated with a
    ABENDEC3/ABENDSEC3 REASON 04130004, 04130007, 04130008, or
    0413000A.
    .
    An alternative scenario is that the Servant is not terminated
    . but the timeout message BBOO00327I contains Servant
    . information (e.g. ASID(xxxx)) even though the request was
    . cleaned up prior to dispatch.
    

Problem conclusion

  • Code has been modified in the request timeout processing
    routines dealing with WLM queue percent to eliminate the
    ability of the request state to progress once the WLM queue
    percent timeout processing has determined that the request needs
    to be recovered.
    
    APAR PI06958 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.33, 8.0.0.9, and 8.5.5.2
    of WebSphere Application Server.
    
    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

    PI06958

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-26

  • Closed date

    2013-12-20

  • Last modified date

    2014-07-01

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI18561

       UP14/06/21 P F406

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022