MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  FDC with the Probe ID: RM008005

    Posted Wed July 29, 2020 06:17 AM

    Hi, I would like to ask for more information about the following FDC which has been generated on our system:

    +-----------------------------------------------------------------------------+
    | |
    | IBM MQ First Failure Symptom Report |
    | ========================================= |
    | |
    | Date/Time :- Wed July 29 2020 11:33:10 CEST |
    | UTC Time :- 1596015190.563923 |
    | UTC Time Offset :- 120 (CET) |
    | Host Name :- xyz |
    | Operating System :- Linux 4.14.35-1902.302.2.el7uek.x86_64 |
    | PIDS :- 5724H7251 |
    | LVLS :- 9.1.0.5 |
    | Product Long Name :- IBM MQ for Linux (x86-64 platform) |
    | Vendor :- IBM |
    | O/S Registered :- 1 (libmqmcs_r.so) |
    | Data Path :- /var/mqm |
    | Installation Path :- /opt/mqm |
    | Installation Name :- Installation1 (1) |
    | License Type :- Production |
    | Probe Id :- RM008005 |
    | Application Name :- MQM |
    | Component :- rrxStopChannel |
    | SCCS Info :- /build/slot2/p910_P/src/lib/remote/amqrcmsa.c, |
    | Line Number :- 2451 |
    | Build Date :- Apr 1 2020 |
    | Build Level :- p910-005-200401 |
    | Build Type :- IKAP - (Production) |
    | Effective UserID :- 1000 (mqm) |
    | Real UserID :- 1000 (mqm) |
    | Program Name :- amqrmppa |
    | Arguments :- -m XZY |
    | Addressing mode :- 64-bit |
    | LANG :- en_US.UTF-8 |
    | Process :- 18302 |
    | Process(Thread) :- 71510 |
    | Thread :- 473966 RemoteResponder |
    | QueueManager :- XZY |
    | SubpoolName :- XZY |
    | UserApp :- FALSE |
    | ConnId(1) IPCC :- 1605479 |
    | ConnId(3) QM-P :- 1515241 |
    | Last HQC :- 1.6.6-3081728 |
    | Last HSHMEMB :- 0.0.0-0 |
    | Last ObjectName :- |
    | Major Errorcode :- OK |
    | Minor Errorcode :- OK |
    | Probe Type :- INCORROUT |
    | Probe Severity :- 4 |
    | Probe Description :- AMQ6125E: An internal IBM MQ error has occurred. |
    | FDCSequenceNumber :- 2 |
    | |
    +-----------------------------------------------------------------------------+

    I could only find the following post related to an similar issue is the following:

    http://www.mqseries.net/phpBB2/viewtopic.php?t=76706&sid=e3602cda25bb8c424832027e4435de12

    But I can't see there any solution.

    Related error log snipet:
    ----- amqrmrsa.c : 285 --------------------------------------------------------
    07/29/2020 11:33:07 AM - Process(18302.459682) User(mqm) Program(amqrmppa)
    Host(xyz) Installation(Installation1)
    VRMF(9.1.0.5) QMgr(XZY)
    Time(2020-07-29T09:33:07.313Z)
    CommentInsert1(CHANNEL)

    AMQ9528W: User requested channel 'CHANNEL' to be stopped.

    EXPLANATION:
    The channel is stopping because of a request by the user.
    ACTION:
    None.
    ----- amqrmssa.c : 3367 -------------------------------------------------------


    This stop was not caused by an user. Is this behavior normal? What can cause the stop and could we prevent it?

    Thank you!



    ------------------------------
    Erika Fődi
    ------------------------------


  • 2.  RE: FDC with the Probe ID: RM008005

    Posted Wed July 29, 2020 10:55 AM
    I have seen this behavior when we upgraded to 9.1 last year, too.  It does not happen too often, but we get these sporadic FDC errors in the stopChannel code with the corresponding "channel is stopping" message in the queue manager error logs.  No admin is doing a manual stop channel when this happens.  We have not seen any actual issues with channels when this error message gets produced.

    ------------------------------
    Tim Zielke
    ------------------------------

    Original Message


  • 3.  RE: FDC with the Probe ID: RM008005

    Posted Wed July 29, 2020 11:04 AM
    Thank you Tim! So your opinion is that this could be a "childhood disease" by 9.1 and can be ignored? We received this FDC today twice and last week one time. I'm not worried about it yet, but it would be good to know the cause for it.

    ------------------------------
    Erika Fődi
    ------------------------------

    Original Message


  • 4.  RE: FDC with the Probe ID: RM008005

    Posted Wed July 29, 2020 11:14 AM
    I personally have been ignoring it, as it does not seem to result in any actual channel issues in MQ.

    ------------------------------
    Tim Zielke
    ------------------------------

    Original Message


  • 5.  RE: FDC with the Probe ID: RM008005

    Posted Wed July 29, 2020 11:18 AM
    Thanks!

    ------------------------------
    Erika Fődi
    ------------------------------

    Original Message