| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Program amqrmppa |
« View previous topic :: View next topic » |
| Author |
Message
|
| rjl_state |
 Posted: Wed Jun 11, 2008 7:00 am Post subject: MQ Program amqrmppa |
 |
|
Apprentice
Joined: 04 Oct 2002
Posts: 48
Location: Des Moines, IA
|
I am getting the following message on my system on some days, I hope someone can explain it to me. Thanks!
This is on a NSK Tandem running 5.3 under OSS.
------------------------------------------------------------------------
06/11/08 08:19:39 Process(3,584 67 $X1967) User(MQM.MGR) Program(amqrmppa_r)
AMQ9209: Connection to host 'xyz (10.50.100.101)' closed.
EXPLANATION:
An error occurred receiving data from 'xyz (10.50.100.101)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- .\amqccssl.c : 2857 -----------------------------------------------------
06/11/08 08:19:39 Process(3,584 67 $X1967) User(MQM.MGR) Program(amqrmppa_r)
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0. |
|
| Back to top |
|
 |
| hankknowles |
| Posted: Thu Jun 12, 2008 6:35 am Post subject: Re: MQ Program amqrmppa |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| rjl_state wrote: |
I am getting the following message on my system on some days, I hope someone can explain it to me. Thanks!
This is on a NSK Tandem running 5.3 under OSS.
------------------------------------------------------------------------
06/11/08 08:19:39 Process(3,584 67 $X1967) User(MQM.MGR) Program(amqrmppa_r)
AMQ9209: Connection to host 'xyz (10.50.100.101)' closed.
EXPLANATION:
An error occurred receiving data from 'xyz (10.50.100.101)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- .\amqccssl.c : 2857 -----------------------------------------------------
06/11/08 08:19:39 Process(3,584 67 $X1967) User(MQM.MGR) Program(amqrmppa_r)
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0. |
Think that might have been resolved in a fix pak - you got to love these error messages and the FDC too! One day we will get better and complete message sets from IBM!
I used to see similar messages until we went to V53.1.1_patch3 seemed to fix it pretty much. V53.1.2 is buggy in a couple of areas mostly TMF from what I am seeing in notes from IBM support. I also noted yesterday the IBM will be dropping V53.1.3 sometime soon! The apar was created to allow creation of a PTF package!
The net of my suggestion is get to V53.1.1_patch3 - make sure the network is solid between the NSK and the remote server! If it's a client accessing maybe they need to get to a higher version in client code!
HTH |
|
| Back to top |
|
|
| rjl_state |
| Posted: Fri Jun 13, 2008 7:11 am Post subject: |
|
|
Apprentice
Joined: 04 Oct 2002
Posts: 48
Location: Des Moines, IA
|
Thanks for your response.
We are on v5.3.1.1 patch 3.
/: mqver
Name: WebSphere MQ
Version: 531.1 FP5311
CMVC level: WMQ-5-3-1-1
BuildType: IKAP - (Production)
Thankfully we avoided 5.3.1.2.
This sounds like an oss resource issue, but I don't know where to look for errors other than the mq error files and the guardian console log.
I don't want to open an issue with IBM because they will just tell me to upgrade to 5.3.1.2 patch 1. It could be that stopping and restarting MQ may clear the problem up for a while.
I guess I will wait for 5.3.1.3 and see what that looks like. |
|
| 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
|
|
|
|
