MQ

 View Only
  • 1.  Seek help MQ ffdc file rootcause

    Posted Mon December 19, 2022 08:06 PM
    +-----------------------------------------------------------------------------+
    |                                                                             |
    | WebSphere MQ First Failure Symptom Report                                   | 
    | =========================================                                   | 
    |                                                                             |
    | Date/Time         :- Fri December 16 2022 00:45:28 CST                      | 
    | UTC Time          :- 1671122728.110638                                      | 
    | UTC Time Offset   :- 480 (CST)                                              | 
    | Host Name         :- srv1_xdzf                                              | 
    | Operating System  :- AIX 6.1                                                | 
    | PIDS              :- 5724H7221                                              | 
    | LVLS              :- 7.0.1.3                                                | 
    | Product Long Name :- WebSphere MQ for AIX                                   | 
    | Vendor            :- IBM                                                    | 
    | Probe Id          :- RM293020                                               | 
    | Application Name  :- MQM                                                    | 
    | Component         :- AddFreeChain                                           | 
    | SCCS Info         :- lib/remote/amqrfica.c, 1.109.1.1                       | 
    | Line Number       :- 3426                                                   | 
    | Build Date        :- Aug 12 2010                                            | 
    | CMVC level        :- p701-103-100813                                        | 
    | Build Type        :- IKAP - (Production)                                    | 
    | Effective UserID  :- 12 (mqm)                                               | 
    | Real UserID       :- 12 (mqm)                                               | 
    | Program Name      :- amqrrmfa                                               | 
    | Addressing mode   :- 64-bit                                                 | 
    | Process           :- 9437266                                                | 
    | Thread            :- 1                                                      | 
    | QueueManager      :- QMMC                                                   | 
    | UserApp           :- FALSE                                                  | 
    | ConnId(1) IPCC    :- 20                                                     | 
    | ConnId(2) QM      :- 22                                                     | 
    | Last HQC          :- 1.0.0-683896                                           | 
    | Last HSHMEMB      :- 1.2.2-13024                                            | 
    | Major Errorcode   :- OK                                                     | 
    | Minor Errorcode   :- OK                                                     | 
    | Probe Type        :- INCORROUT                                              | 
    | Probe Severity    :- 4                                                      | 
    | Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred.  | 
    | FDCSequenceNumber :- 3                                                      | 
    |                                                                             |
    +-----------------------------------------------------------------------------+


    Dears,MQ 7.0.1 generated such ffdc,Anyone can help analyze it?Thanks.


    ------------------------------
    DONG SHENG CHEN
    ------------------------------


  • 2.  RE: Seek help MQ ffdc file rootcause

    IBM Champion
    Posted Tue December 20, 2022 02:24 AM

    An MQ user can only analyse the header of a FFDC really by doing a web search on the probe ID, in this case, RM293020. I don't see any hits on MQ APARs mentioning this probe ID. Any more in-depth analysis of an FFDC file (the remaining contents that you have not shown us in your post) would be done by raising a case (previously known as a PMR) with IBM.

    IBM WebSphere MQ V7.0.1 is however, long out of service, so I don't believe IBM would do this analysis for you either. However, you are using a very very old fix pack of very very old MQ version. You appear to only be on fix pack 3

    LVLS              :- 7.0.1.3

    If you have any hope of finding a fix for this issue in the MQ version 7.0.1, you could try upgrading to the latest fix pack of that version which is fix pack 14, which was released in August 2016.

    However, better advice would be to move to a version of MQ that is in service, for example IBM MQ V9.3.0. That way, if you encounter a problem, you can ask IBM to fix it.

    I see from your FFDC file header that you are on

    Operating System  :- AIX 6.1 

    I believe the oldest version of MQ you can use with that O/S is V8.0.0 which is also out of service. So you should also be thinking about upgrading your O/S.

    Sorry not to be of more help.

    Cheers,
    Morag



    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    Website: https://www.mqgem.com
    ------------------------------



  • 3.  RE: Seek help MQ ffdc file rootcause

    Posted Tue December 20, 2022 02:45 AM
    Thanks your reply.

    ------------------------------
    DONG SHENG CHEN
    ------------------------------



  • 4.  RE: Seek help MQ ffdc file rootcause

    Posted Tue December 20, 2022 02:34 AM

    Hello.

    When did you get this message?  Does a qmgr restart solved the problem?

    This can be a hang or cache related problem.

    Also, you are on MQ 7.0.1.3. The latest fixpack is 7.0.1.14



    ------------------------------
    rniew
    IT Spe
    IBM
    (49171) 722-9761
    ------------------------------



  • 5.  RE: Seek help MQ ffdc file rootcause

    Posted Tue December 20, 2022 02:50 AM
    Custome killed their application,it is a C programm,and visit QMGR via binding method.
    After they killed this C program,the ffdc files were generated. 
    Yes ,it is resolved  by restart QMGR.

    ------------------------------
    DONG SHENG CHEN
    ------------------------------



  • 6.  RE: Seek help MQ ffdc file rootcause

    IBM Champion
    Posted Tue December 20, 2022 03:41 AM
    This looks so out of data you may not get any help.
    I suspect you will not be able to migrate to the next release, because I expect the next release is also out of service and unobtainable.
    I recommend you install the latest version, and move your definitions etc to that.
    Colin





  • 7.  RE: Seek help MQ ffdc file rootcause

    Posted Tue December 20, 2022 03:43 AM
    I would say open a support case with IBM, but they would point out that MQ 7.0.1.3 is very old and not supported. So I suggest framing this one.

    ------------------------------
    Peter T
    ------------------------------



  • 8.  RE: Seek help MQ ffdc file rootcause

    Posted Tue December 20, 2022 03:54 PM
    This is an error reported by an MQ internal process (amqrrmfa) indicating that MQ internal state has been corrupted.
    It's not completely impossible for an application error (e.g. shared memory overwrite) to lead to this sort of outcome, but it would be extremely unlikely and it's therefore much more likely to be an APARable MQ error. That being said, as others have pointed out  your service level is ancient and therefore IBM is unlikely to help.
    If you really did suspect some application of causing this issue then configuring that app to use isolated bindings would eliminate any possibility of that application being able to corrupt MQ internal state.
    The type of storage that has been found to be corrupt would all be completely refreshed by a queue manager restart, the worry being whether the error could reoccur some indeterminate time after the restart.

    Note also that this is the third FDC to have been raised by that instance of the amqrrmfa process, it would be interesting to know what the previous two errors reported (and when they were repored).

    Presumably with such an ancient service level, this system has been stable for a long time ? Have ANY recent changes been made to this system ?

    ------------------------------
    Andrew Hickson
    ------------------------------



  • 9.  RE: Seek help MQ ffdc file rootcause

    Posted Wed December 21, 2022 01:15 AM
    Thanks for your advice.  @Andrew Hickson

    ------------------------------
    DONG SHENG CHEN
    ------------------------------