| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| SOLVED: AMQ9228: The TCP/IP responder program |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Wed Jul 05, 2006 2:26 pm Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
As a suggestion, also, if you are running Oracle anywhere in your enterprise, I would suggest avoiding use of port 1521 for your MQ listeners.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| jon |
| Posted: Sat Jul 25, 2009 10:23 pm Post subject: |
|
|
Apprentice
Joined: 17 May 2009
Posts: 32
|
I am also getting the same error, although the MQ logs also say problem with SSL but I don't see one in my configuration.
this is the logs I am getting on the receiver Queue Manager-
| Quote: |
----- amqrmrsa.c : 457 --------------------------------------------------------
07/26/2009 01:18:32 PM
AMQ9660: SSL key repository: password stash file absent or unusable.
EXPLANATION:
The SSL key repository cannot be used because MQ cannot obtain a password to
access it. Reasons giving rise to this error include:
(a) the key database file and password stash file are not present in the
location configured for the key repository,
(b) the key database file exists in the correct place but that no password
stash file has been created for it,
(c) the files are present in the correct place but the userid under which MQ is
running does not have permission to read them,
(d) one or both of the files are corrupt.
The channel is '????'; in some cases its name cannot be determined and so is
shown as '????'. The channel did not start.
ACTION:
Ensure that the key repository variable is set to where the key database file
is. Ensure that a password stash file has been associated with the key database
file in the same directory, and that the userid under which MQ is running has
read access to both files. If both are already present and readable in the
correct place, delete and recreate them. Restart the channel.
----- amqccisx.c : 1103 -------------------------------------------------------
07/26/2009 01:18:32 PM
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.
|
In my case, the receiver box is Linux and the websphere MQ version is 530.13 CSD13, whereas the sender is a Windows box and with version 6.0.2.4.
I dont see any problem with SSL, as all the configuration is set properly and we are able to start the sender from Linux to Windows. Then why there is a SSL problem in Windows --> Linux?
Further to add, while starting the channel from Windows to Linux, it goes into retrying mode but the Substate is blank, but sometimes it goes in Binding mode and shows the Substate as "NAMESERVER".
It is not writing any logs on Sender(Windows) side, but it writes the log on the receiver end(shown above) on Linux server. |
|
| Back to top |
|
|
| jon |
| Posted: Sun Jul 26, 2009 12:19 am Post subject: |
|
|
Apprentice
Joined: 17 May 2009
Posts: 32
|
Hello everyone, the problem is resolved. there was some issue on the listener of receiver queue manager. I came to know about this when I try to ping from the sender channel and got the error "Connection Closed". Generally if its a SSL problem, ping still will work. But as ping was not working so I went to the receiver queue manager listener and restarted it.
Thanks to everyone for reading my post. |
|
| Back to top |
|
|
| KIDINMQ |
| Posted: Mon Oct 28, 2024 8:08 am Post subject: How was it resolved ? |
|
|
Novice
Joined: 12 Nov 2013
Posts: 15
|
The below link is expired and not able to understand how it was resolved ?
http://www-1.ibm.com/support/docview.wss?doc=aimwmq&rs=171&uid=swg21110505
Was it the issue at local MQ ? or the issue with the applications connected to local MQ ?, in my case; I am getting this AMQ9228 on Solaris and applications connects to this MQ to consume Messages in batches. And now the data isn't moving since 2 days. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Oct 28, 2024 3:40 pm Post subject: Re: How was it resolved ? |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2536
Location: Melbourne, Australia
|
| KIDINMQ wrote: |
| ... in my case; I am getting this AMQ9228 on Solaris and applications connects to this MQ to consume Messages in batches. And now the data isn't moving since 2 days. |
What version of MQ are you running on Solaris? (It may predate the MQ LISTENER object feature)
netstat -an | grep LISTEN
Check if MQ is listening on the port that the MQ client app or remote MQ sender channel is trying to use.
If the listener is running, try killing & restarting it.
ps -ef | grep runmqlsr
ps -ef | grep amqcrsta (usually started by inetd using entry in /etc/services -- That's stretching my memory a bit)
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
