MQSeries.net :: View topic

ajith.rajan · Posted: Fri Feb 11, 2005 8:32 am Post subject:

Hi

We are currently working on a project which would have a Alteon load balancer in front of two MQ Servers.
The Alteon would healthcheck one of the MQ Servers by identifying if the listener process for our Q Manager is running fine. If the healthcheck fails, it forwards the messages to the other MQ Server.

We had almost completed with this when we identified that the following error messages are logged in the Error logs of the QManager whenever the Alteon checks for the MQ Listener process.

*******************************************************************************
----- amqrmrsa.c : 461 --------------------------------------------------------
02/04/05 10:13:26
AMQ9209: Connection to host 'uslond1-101-if21 (192.146.34.132)' closed.

EXPLANATION:
An error occurred receiving data from 'uslond1-101-if21 (192.146.34.132)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2781 -------------------------------------------------------
02/04/05 10:13:26
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.
----- amqrmrsa.c : 461 --------------------------------------------------------
*******************************************************************************

We identified that the host name as mentioned in the log file (192.146.34.132) is the IP of the Alteon load balance and the error is thrown whenever the alteon checks for the listener process in the MQ Server.
This causes lots of unuseful informations getting logged in our Error Log file. This also increases the log file size leading to disk space constraints.

Can anyone help me out in preventing these unuseful errors getting logged??

Thanks
Ajith