IBM Support

PM86478: MDB MESSAGES WERE QUEUED TO A SERVANT THAT IS NOT READY FOR WORK YET.

Fixes are available

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Customer running with :
    server_use_wlm_to_queue_work = 0
    server_work_disribution_algorithm = 2 (hot robin )
    While one servant was being brought up, messages arrived were
    queued to that servant even though the servant was not
    readyforwork. SrqeReadyForWork flag should be checked before
    messages can be queued to the servant.
    .
    Additional Symptom:
    In addition, if the server is configured with
    wlm_minimumSRCount=1 and wlm_maximumSRCount=2
    and
    the server starts up a CRA region (an Adjunct region), then all
    the incoming work will end up queued to the one servant
    region's queue, but the runtime never checks for work there.
    It only chec CRA's queue and the one servant's work queue is
    never checked for available work.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5 on z/OS         *
    ****************************************************************
    * PROBLEM DESCRIPTION: MDB requests queued to a                *
    *                      WebSphere Application Server for z/OS   *
    *                      servant that is not ready to process    *
    *                      work timeout.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running with server_use_wlm_to_queue_work = 0 and
    server_work_distribution_algorithm=2, MDB requests timeout
    because they were queued to a servant that was not
    ready to process work. A Servant that is in the process of
    starting up is considered not ready to process work.
    BBOO0327I MDB Plan "A" REQUEST TIMEOUT:
    (0000):(FFFF6521):(00020005):(00000000):():
    (2013/03/21 15:03:02.592877):
    (2013/03/21 15:03:02.610996):():(mdbclass):
    (mdbrequest):(Local to this Server):():():
    (CmdOltpLsr04)
    

Problem conclusion

  • Changed the code to skip servants that are not ready to
    process work.
    
    APAR PM86478 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.31, 8.0.0.7, and 8.5.5.1.
    
    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

    PM86478

  • 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-04-05

  • Closed date

    2013-04-25

  • Last modified date

    2014-02-05

  • 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 UI13725

       UP14/01/11 P F401

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

Reference #: PM86478

Modified date: 05 February 2014