| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel terminated with RM487001 & AMQ9604 |
« View previous topic :: View next topic » |
| Author |
Message
|
| pshan81 |
 Posted: Thu Mar 19, 2009 12:21 am Post subject: Channel terminated with RM487001 & AMQ9604 |
 |
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
Hi All,
Channels are getting terminated unexpectedly in one of our test box with AMQ9604 error.AMQ6109 error is also thrown. We are using MQ 5.3 CSD10 in AIX 5.2 (We are upgrading to 6.0.2.5 soon).
Below are the two FDC files being generated
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday March 19 15:15:24 TAIST 2009 |
| Host Name :- sgcit23 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- RM487001 |
| Application Name :- MQM |
| Component :- rriChannelTerminate |
| Build Date :- May 12 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (mqm) |
| Program Name :- amqrmppa |
| Process :- 04849764 |
| Thread :- 00000012 |
| QueueManager :- SGCIT23 |
| Major Errorcode :- rrcE_CHANNEL_TERMINATED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9604 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9604: Channel 'SGCIT02.SGCIT23' terminated |
| unexpectedly |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545284357 20806105 |
| Arith2 :- 6541366 63d036 |
| Comment1 :- SGCIT02.SGCIT23 |
| Comment2 :- |
| Comment3 :- |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ccxResponder
rrxResponder
rriAcceptSess
rriAddStatusEntry
rriChannelTerminate
xcsFFST
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday March 19 15:11:20 TAIST 2009 |
| Host Name :- sgcit23 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC130006 |
| Application Name :- MQM |
| Component :- xehExceptionHandler |
| Build Date :- May 12 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (mqm) |
| Program Name :- amqrmppa |
| Process :- 06541366 |
| Thread :- 00000000 |
| QueueManager :- SGCIT23 |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 11 b |
| Comment1 :- SIGSEGV |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xppRunDestructors
ziiClearUpAgent
zcpSendOnPipe
xcsResetEventSem
xcsFFST
Segmentation violation signal is thrown by Unix for amqrmppa process.File permissions for /usr/mqm and /var/mqm are there for "mqm" user and the file system is only 80% occupied. IBM suggests the below
http://www-01.ibm.com/support/docview.wss?uid=swg21188574
I also noticed that amqrmppa is being killed and restarted.Should it be running always? (or) Is it a normal behaviour?
mqm 6041770 5853436 0 15:51:18 pts/10 0:00 grep amqrmppa
mqm 1286212 643148 0 15:34:41 - 0:00 /usr/mqm/bin/amqrmppa -m SGCIT23
mqm 8147120 5853436 1 15:51:19 pts/10 0:00 grep amqrmppa
mqm 1286214 5853436 0 15:51:20 pts/10 0:00 grep amqrmppa
mqm 4075756 5853436 1 15:51:22 pts/10 0:00 grep amqrmppa
mqm 4075534 5853436 0 15:51:31 pts/10 0:00 grep amqrmppa
mqm 8294606 643148 1 15:51:34 - 0:00 /usr/mqm/bin/amqrmppa -m SGCIT23 |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Mar 19, 2009 12:57 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If you are going to upgrade soon, and as this is a test box, why are you bothering to try and resolve this? Use it as an opportunity to upgrade now, then see if the problem remains. You could spend more time and effort trying to sort this out than it would to upgrade...plus you'll be able to raise a PMR if necessary.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| pshan81 |
| Posted: Fri Mar 20, 2009 6:30 am Post subject: |
|
|
Acolyte
Joined: 24 May 2005
Posts: 72
|
| Quote: |
| If you are going to upgrade soon, and as this is a test box, why are you bothering to try and resolve this? Use it as an opportunity to upgrade now, then see if the problem remains |
Thanks exerk. Feared of the occurence of this error in production! very much interested in solving the MQ issues.
I also noticed that amqrmppa is running all the time in other environments.We also took a trace of the process and amqrmppa is exiting with 11 (_exit11). So it is not being killed.
Did any one come across this error? Is there any other solution or workaround for the issue. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Mar 20, 2009 6:41 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| pshan81 wrote: |
| Thanks exerk. Feared of the occurence of this error in production!... |
If it does, you will still be in the position of being unable to raise a PMR should that be the only recourse to resolving the issue. Upgrade the box, see if the problem is still extant, and then fault diagnose.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 6:46 am Post subject: Re: Channel terminated with RM487001 & AMQ9604 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pshan81 wrote: |
I also noticed that amqrmppa is being killed and restarted.Should it be running always? (or) Is it a normal behaviour?
|
They should stop and start as the channels require. More noted (at your level of WMQ) for going crazy and chewing CPU than they are for stopping unexpectedly.... 
I agree with my associate - if you're planning to upgrade, advance the process and retest. As a bare minimum, move to the latest version of WMQv5.3
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
