| Author |
Message
|
| Tibor |
 Posted: Mon Sep 20, 2004 12:10 am Post subject: qmgr collapse on Tandem |
 |
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
We've got the next error messages in the error log files, and all the queue manager functionality stopped.
| Quote: |
--------------------------------------------------------------------------------
2004/09/20 08.32.06
AMQ8640: Signal delivery timeout expired for an MQGET.
EXPLANATION:
The Queue Server process $MQSS failed to open and send a signal to the
application process \PING.$Y841 within the timeout allowed for signal delivery.
The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been
cancelled by the Queue Server, but no notification can be delivered to the
application.
ACTION:
Manual intervention with the application may be necessary to ensure that it
resumes normal processing. No further notification will be delivered to the
application relating to the MQGET call that established the signal. The
application can re-open the queue and re-issue the MQGET call to recover from
this situation.
-------------------------------------------------------------------------------
2004/09/20 08.32.07
AMQ8640: Signal delivery timeout expired for an MQGET.
EXPLANATION:
The Queue Server process $MQSS failed to open and send a signal to the
application process \PING.$Y844 within the timeout allowed for signal delivery.
The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been
cancelled by the Queue Server, but no notification can be delivered to the
application.
ACTION:
Manual intervention with the application may be necessary to ensure that it
resumes normal processing. No further notification will be delivered to the
application relating to the MQGET call that established the signal. The
application can re-open the queue and re-issue the MQGET call to recover from
this situation.
-------------------------------------------------------------------------------
|
I had to stop all qmgr processes manually, because endmqm didn't response, too.
MQ version: MQ5.1 CSD02 + EFix6
Has anyone ever seen similar?
Thanks in advance,
Tibor |
|
| Back to top |
|
 |
| LuisFer |
| Posted: Mon Sep 20, 2004 5:59 am Post subject: Re: qmgr collapse on Tandem |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Our MQ is on CSD2 Efix2. It's the first time that i see this one, but we haven't any appls. working with signalling.(on Tandem).
I'll make a probe & answer. |
|
| Back to top |
|
|
| hankknowles |
| Posted: Tue Sep 21, 2004 4:03 am Post subject: qmgr collapse on Tandem |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
Hi Tibor:
Happens quite often on out test development system, I have traced some of the problem to QPASA holding onto something, when I do a graceful shutdown of the 3 qmgrs on this box my script tries 5 times to do endmqm -q and after that it issues the immediate stop. When the script hits this point it also does an [#if[#processexists] $qmgr server and it kills the process. Of course when this does happen the qmanager and pathway kinda react weirdly on restart and sometimes I need to do another endmqm then restart ( I haven't investigated why completely). Of course also understand our qmgrs get killed maybe once every 6 month's due to upgrade or cold loads. We also are on CSD02 plus efix3 or 4. Had to back out efix6 as the client was having transaction abort issues. The vendor is fixing their code and I hope to be back to efix6.
HTH  |
|
| Back to top |
|
|
| Tibor |
| Posted: Tue Sep 21, 2004 4:54 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Hank,
It sounds like a conspiration  because we have QPasa agent on Tandem, too. Finally I found the malicious code 
Tibor |
|
| Back to top |
|
|
| hankknowles |
| Posted: Tue Sep 21, 2004 5:00 am Post subject: qmgr collapse on Tandem |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
Sounds that way too! We had an issue that if you pulled a qmgr down with QPASA running it would go off and spawn a looping process. The solution was kill QPASA completely before shutting down. Then it would be better behaved?  .... I no longer argue just do it and move on. Also if you happen to start a trace on a qmgr QPASA starts a log and won't let go even after you end the trace, you have to kill QPASA and restart. Given these minor headaches QPASA is pretty much well behaved I have seen way worse trust me, especially in my last life with AS/400 and CA-Unicenter YUK!! Cheers
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 21, 2004 5:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's probably a good idea to shut down any MQ monitoring agent before a queue manager shutdown.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 21, 2004 7:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Jeff,
| Quote: |
| It's probably a good idea to shut down any MQ monitoring agent before a queue manager shutdown. |
We are running QPasa on machines with multiple qmgrs and are not having any of these problems. We run a nightly offline backup and do not shutdown QPasa for it. There is no problem shutting down a qmgr while QPasa is running.
We shutdown the qmgrs in IMMEDIATE mode (-i)...
Env MQ 5.3 + CSD07 / CSD06 on AIX/Solaris
We had a tiny problem with CSD06 because rcdmqimg could not wrap around temp queues(qpasa) and had to get the interim fix...
This should be so by design...
We monitor as well boxes still on 5.2.. I know no longer supported, trying to get them to 5.3 if the Apps folks will give me a maintenance window..
Enjoy  |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Sep 22, 2004 12:18 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Quote: |
| We are running QPasa on machines with multiple qmgrs and are not having any of these problems. |
Agree in most case... but have you got Tandem?
Tibor |
|
| Back to top |
|
|
| kfhickel |
| Posted: Wed Sep 22, 2004 7:44 am Post subject: Re: qmgr collapse on Tandem |
|
|
Newbie
Joined: 30 Dec 2001
Posts: 9
|
| hankknowles wrote: |
Sounds that way too! We had an issue that if you pulled a qmgr down with QPASA running it would go off and spawn a looping process. The solution was kill QPASA completely before shutting down. Then it would be better behaved? .... I no longer argue just do it and move on. Also if you happen to start a trace on a qmgr QPASA starts a log and won't let go even after you end the trace, you have to kill QPASA and restart. Given these minor headaches QPASA is pretty much well behaved I have seen way worse trust me, especially in my last life with AS/400 and CA-Unicenter YUK!! Cheers
|
Hank and Tibor,
I'd like to urge you both to contact MQSoftware support about these issues. When I saw the thread on the board, I went back and tested the currently shipping agent on tandem and have no issues shutting down a qmgr (controlled or immediate) and bringing it back up. I searched past bugs and found some bug reports from each of you on the tandem, although the only exact match was the one Hank mentioned about qpmon looping. In each of these cases we suggested you upgrade to the then current agent version and see if there were any further issues. From what I can tell, neither of you came back to us with any problems, and eventually we closed the bugs after contacting you.
As far as qpasa seeming to block the restart of a queue manager, that was occasionally seen on various platforms, but only with MQ 5.1 and only specific MQ fix levels, thus it appears to have been an IBM issue. There are no remaining issues like this on any platform that I can find.
It's very important that you let us know when you have long standing issues like this, we don't want you to just have to live with these problems.
Sincerely,
Kelly Hickel
Senior Product Architect
MQSoftware, Inc. |
|
| Back to top |
|
|
| hankknowles |
| Posted: Wed Sep 22, 2004 8:00 am Post subject: qmgr collapse on Tandem |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
Hi Kelly:
Yes the problem was resolved as far as I can tell, just sharing information with others! |
|
| Back to top |
|
|
| kfhickel |
| Posted: Wed Sep 22, 2004 8:02 am Post subject: Re: qmgr collapse on Tandem |
|
|
Newbie
Joined: 30 Dec 2001
Posts: 9
|
| hankknowles wrote: |
Hi Kelly:
Yes the problem was resolved as far as I can tell, just sharing information with others! |
Hi Hank,
That's no problem, I was just concerned by your comment "I no longer argue just do it and move on", that sounds like you're still having an issue where you have to stop qpmon if you're going to stop the qmgr. You shouldn't have to do that.
-Kelly |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 22, 2004 6:50 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remember as well to close the Tree involving the qmgr in the configuration manager before shutting dow the qmgr. This is like keeping a process on the qmgr and it won't start. Just elementary precautions...
Enjoy |
|
| Back to top |
|
|
| LuisFer |
| Posted: Thu Sep 23, 2004 11:05 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Hi all:
I made a probe without problems.
I remember a Trial with the Candle's Monitor MQ for Tandem (MQ on V2201) and happen a similar problem, in this case was the Process Agent on Loop.
Other thing, i probed the new MO72 SP & it's a great util.
Two or three months ago, i write a little pgm on C (MQAI , Escape_Pcf) that works equal to MO72 but for the Tandem Platform , for admin purpuoses.
If , someone wants to see it, tell me (translated to English, too).
Regards |
|
| Back to top |
|
|
|
|
