| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channels terminated... |
« View previous topic :: View next topic » |
| Author |
Message
|
| aboggis |
 Posted: Tue Aug 03, 2004 5:17 pm Post subject: Channels terminated... |
 |
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I am getting a bunch of errors in the global log file (/var/mqm/errors/AMQERR01.LOG) like the following:
| Code: |
----- amqxfdcx.c : 707 --------------------------------------------------------
08/03/04 17:54:43
AMQ9604: Channel 'TO.PP.AR1' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'TO.PP.AR1' is no longer running. The
check process system call returned 545284357 for process 5716.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated.
----- amqxfdcx.c : 673 --------------------------------------------------------
08/03/04 17:54:43
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
CLUSTERP.PPAR1.MANAGER.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 9613.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 707 --------------------------------------------------------
|
In looking in the generated FDC files I see the following:
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tuesday August 03 16:36:13 GMT 2004 |
| Host Name :- ss44bsppar01 (SunOS 5.8) |
| PIDS :- 5724B4103 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- RM487001 |
| Application Name :- MQM |
| Component :- rriChannelTerminate |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000300 (mqm) |
| Program Name :- amqrmppa |
| Process :- 00025452 |
| Thread :- 00000026 |
| QueueManager :- CLUSTERP!PPAR1!MANAGER |
| Major Errorcode :- rrcE_CHANNEL_TERMINATED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9604 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9604: Channel 'TO.PP.AR1' terminated unexpectedly |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545284357 20806105 |
| Arith2 :- 7905 1ee1 |
| Comment1 :- TO.PP.AR1 |
| |
| Comment2 :- |
| |
| Comment3 :- |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ccxResponder
rrxResponder
rriAcceptSess
rriAddStatusEntry
rriAdoptMCA
rriChannelTerminate
xcsFFST
MQM Trace History
--------} zcpCreateMessage rc=OK
-------} ziiCreateIPCCMessage rc=OK
-------{ zcpSendOnPipe
--------{ xcsResetEventSem
...
|
I have seen only one similar FFST generated (http://www-1.ibm.com/support/docview.wss?uid=swg1SE13524), but that doesn't seem to be the same.
My environment is Solaris, WMQ 5.3, CSD05.
Any suggestions?
tonyB. |
|
| Back to top |
|
 |
| kman |
| Posted: Tue Aug 03, 2004 7:13 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
| First suggestion, get CSD07 installed |
|
| Back to top |
|
|
| kman |
| Posted: Tue Aug 03, 2004 7:17 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Second suggestion:
Check to see if there is any process or program that is terminating the channel.
Is the channel really terminated?
Is the system low in resources that somehow the system terminate a process, in this case the channel? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Aug 04, 2004 7:02 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Tony,
I don't think it worth getting too worried about these FDCs. If anything it
looks like the product is being a little over zealous in reporting
something odd. From the function stack you can see that we're in AdoptMCA.
(Presumably you have Adopt MCA set on). Essentially a channel has connected
in, MQ has noticed there was an old receiver channel (or whatever) running
and decided to end it. However, before it actually gets the chance to kill
it appears to have gone, probably natural causes. By default MQ will write
an FDC if a channel ends because it looks like somethng has killed it and
it wasn't us. You can generate this behaviour, for example, by stopping a
channel after you've killed it with KILL -9 or task manager.
Anyway, I don't see anything for you to be concerned about. You could raise
a PMR to get service to change the code so we don't issue this FDC in the
case of adoption. If you just want rid of the FDCs you can set an
environment variable MQCHL_NO_TERM_FFST (to anything you like) and we won't
ever print out on of these 'channel terminated' FDCs.
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| aboggis |
| Posted: Wed Aug 04, 2004 7:54 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
As to the suggestion on CSD07... I'd love to.
However, these are prodution level systems and scheduling the outage window on approx 24 hosts is difficult at best. I guess I need to do a better job of "selling" the benifits of CSD07.
I understand that CSD08 is in the pipeline tho'. Is there any hint of an ETA on that?
My reason for wanting to wait for CSD08 is that we are running with an APAR related to a cluster workload exit bug and I was told it is unlikely to be in a CSD until #8 comes out. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Aug 24, 2004 3:42 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
(Sorry for the delay in responding, been away...)
Fixpacks ship at approx 3 months apart, and given the fact the last one was available in June, one might guess at a Sept release of fixpack 8. Note there is no official date, and one reason is that the shipments depends on quality not a date, so if a problem is found then the ship date moves.
What apar were you after? I could check up on its inclusion if you quote a number... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
