IBM Support

PM56984: MDB on remote servant cannot consume any Best effort non persistent messages in ZOS.

Fixes are available

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

  • If consumer application (e.g MDB) is running on different
    application server than the Messaging Engine (ME), MDB cannot
    consume  ᄁ¬ツᆲ モBest effort nonpersistent" messges in ZOS platfor
    Remote servant region (where consumer application deployed)
    throws the following exception during message consumption:
    
    [3/2/12 9:21:39:461 GMT] 0000000c SibRaDispatch 1
    (com.ibm.ws.sib.ra.inbound.impl.SibRaDispatchEndpointActivation)
     [:/8b408b4] Tracing exception:
    com.ibm.ws.sib.comms.common.CommsByteBuffer$CommsSIMessageNotLoc
    kedException: CWSIC8007E: An exception was caught from the
    remote server with Probe Id 3-025-0010. Exception: CWSIP0173E:
    Unable to locate message [<system message ID>] on destination
    <queue name> on messaging engine <ME name>.
     at
    com.ibm.ws.sib.comms.common.CommsByteBuffer.parseSingleException
    (CommsByteBuffer.java:1866)
     at
    com.ibm.ws.sib.comms.common.CommsByteBuffer.getException(CommsBy
    teBuffer.java:1263)
     at
    com.ibm.ws.sib.comms.common.JFAPCommunicator.checkFor_SIMessageN
    otLockedException(JFAPCommunicator.java:1526)
     at
    com.ibm.ws.sib.comms.client.BifurcatedConsumerSessionProxy._read
    AndDeleteSet(BifurcatedConsumerSessionProxy.java:521)
     at
    com.ibm.ws.sib.comms.client.BifurcatedConsumerSessionProxy.readA
    ndDeleteSet(BifurcatedConsumerSessionProxy.java:439)
     at
    com.ibm.ws.sib.ra.inbound.impl.SibRaDispatchEndpointActivation.d
    ispatch(SibRaDispatchEndpointActivation.java:277)
     at
    com.ibm.ws.sib.ra.inbound.impl.SibRaDispatchTarget.dispatch(SibR
    aDispatchTarget.java:94)
    ..
    ..
    
    Mssages other than "Best effort nonpersistent" Quality of
    Service(QoS) can be consumed by remote consumer application
    without any problem in ZOS.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server z/OS V7.0 and V8.0                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: None of the Best Effort Non             *
    *                      Persistent(BENP) messages are           *
    *                      consumed by remotely deployed consumer  *
    *                      application in z/OS.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In z/OS, consumer applications are running on the "servant"
    region and Messaging Engine (ME) is running on the "adjunct"
    region. When consumer application deployed on the remote
    application server which is remote to the ME (e.g ME is
    running on "adjunct" region on server1 and MDB is running on
    "servant" region of server2), the ME delivered the BENP message
    to the remote consumer and deleted the message. The remote
    "servant" region (where consumer runs) initially gets the token
    which is the representation of original message. During message
    consumption, remote "servant" attempted to connect to the local
    ME to obtain the message (for the token). This lead to
    CWSIP0173E error, as the local ME has already deleted BENP
    messages.
    The fix is to keep BENP messages on the ME until consumed by
    the remote consumer application deployed on the remote
    "servant" region. Some times messages can be discarded from
    the heap before message consumption if there is a garbage
    collection request. But this is fine, because as per design it
    is expected to lose some BENP messages. This fix only ensures
    that we do not lose all the BENP messages when consumer
    application is remote to the ME in z/OS.
    

Problem conclusion

  • Source code has been modified to retain BENP messages on the
    ME until message consumption hence we don't lose all
    the BENP messages in z/OS.
    
    APAR PM56984 is currently targeted for inclusion in Fix Pack
    7.0.0.25 of WebSphere Application Server V7.0 and Fix Pack
    8.0.0.4 of WebSphere Application Server V8.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

  • Fix 1:
    
    Add ME on the remote adjunct region which is local to the
    servant region where consumer application is deployed.
    
    Fix 2"
    
    Increase the QoS of the message from BE NP to Reliable Non
    Persistent or higher.
    

Comments

APAR Information

  • APAR number

    PM56984

  • 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

    2012-01-30

  • Closed date

    2012-04-18

  • Last modified date

    2012-11-02

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

       UP12/10/04 P F210

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 #: PM56984

Modified date: 02 November 2012