IBM Support

IC66058: FDC GENERATED WITH PROBE ID KN346096 AFTER APPLYING REFRESH PACKWMQ V7.0.1.0 ON THE WMQ SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After applying the WebSphere MQ V7.0.1 refresh pack, the
    following FDC's are repeatedly generated:
    **********************************************************
    Probe Id          :- KN346096
    Application Name  :- MQM
    Component         :- kpiMQGETM
    SCCS Info         :- lib/lqm/amqkgtma.c, 1.116
    Line Number       :- 2153
    Build Date        :- Aug 13 2009
    CMVC level        :- p000-L090813
    Build Type        :- IKAP - (Production)
    UserID            :- websphere_mq
    Process Name      :- C:\Program Files (x86)\IBM\Web
    \bin\amqzla     |
    a0.exe
    Addressing mode   :- 32-bit
    Process           :- 00002980
    Thread            :- 00000026
    
    UserApp           :- FALSE
    ConnId(1) IPCC    :- 416
    ConnId(2) QM      :- 95
    Last HQC          :- 2.16.16-57956
    Last HSHMEMB      :- 2.16.16-296320
    Major Errorcode   :- MQRC_TRUNCATED_MSG_FAILED
    Minor Errorcode   :- OK
    Probe Type        :- INCORROUT
    Probe Severity    :- 4
    Probe Description :- AMQ6125: An internal WebSphere
    occurred.  |
    FDCSequenceNumber :- 0
    Arith1            :- 4198 1066
    Arith2            :- 4198 1066
    Comment1          :- Message length error
    ******************************************************
    MQM Function Stack
    zlaMainThread
    zlaProcessMessage
    zlaProcessMQIRequest
    zlaMQGETM
    zsqMQGETM
    kpiMQGETM
    xcsFFST
    *********************
    Below is a snippet of the FDC Trace History:
    --------} aqhGetMessage rc=MQRC_TRUNCATED_MSG_FAILED
    --------{ aqsRecoverQOp
    --------} aqsRecoverQOp rc=OK
    -------} aqmGetMessage rc=MQRC_TRUNCATED_MSG_FAILED
    ------} apiGetMessage rc=MQRC_TRUNCATED_MSG_FAILED
    ------{ apiUnlockExclusive
    -------{ xllLongLockRelease
    -------} xllLongLockRelease rc=OK
    ------} apiUnlockExclusive rc=OK
    ------{ atmCompleteOp
    -------{ atmUnlockDataMutex
    --------{ xllLongLockRelease
    --------} xllLongLockRelease rc=OK
    -------} atmUnlockDataMutex rc=OK
    ------} atmCompleteOp rc=OK
    -----} kqiWaitForMessage rc=MQRC_TRUNCATED_MSG_FAILED
    -----{ zrfInsertMQRFH2
    -----} zrfInsertMQRFH2 rc=OK
    -----{ xcsFreeMemFn
    -----} xcsFreeMemFn rc=OK
    -----{ xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere MQ V7.0.1 that get messages using
    asynchronous consume method by setting the MQGMO options field
    with MQGMO_PROPERTIES_FORCE_MQRFH2 bit.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    The FDC with probe id KN346096 is generated if the data length
    returned is greater than the maximum message length requested.
    If the message on the queue is greater than or equal to 4K, then
    retrieving the message using the asynchronous consume method
    with MQGMO options MQGMO_PROPERTIES_FORCE_MQRFH2 set produces
    this FDC. The data length of the message increases when MQRFH is
    inserted to the message retrieved with the pre-generated
    message properties.
    

Problem conclusion

  • The code has been modified so that the data length returned is
    not greater than the maximum message length requested.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    Windows            tbc_p700_0_1_3
    AIX                tbc_p700_0_1_3
    HP-UX (PA-RISC)    tbc_p700_0_1_3
    HP-UX (Itanium)    tbc_p700_0_1_3
    Solaris (SPARC)    tbc_p700_0_1_3
    Solaris (x86-64)   tbc_p700_0_1_3
    iSeries            tbc_p700_0_1_3
    Linux (x86)        tbc_p700_0_1_3
    Linux (x86-64)     tbc_p700_0_1_3
    Linux (zSeries)    tbc_p700_0_1_3
    Linux (Power)      tbc_p700_0_1_3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC66058

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-05

  • Closed date

    2010-02-26

  • Last modified date

    2010-03-04

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2010