| Author |
Message
|
| mqwbiwf |
 Posted: Thu Oct 26, 2006 7:41 am Post subject: AMQ9208 and 9209 |
 |
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
Hi,
We have one QMgr on AIX and the other on Win2003(both MQ 5.3 CSD 8 ). Those QMgr logs are being filled up with AMQ9208 and AMQ9209 error msgs respectively. After some research, I found that it's becoz the MQ client didn't disconnect from the server in a clean fashion.
I would like to know what should be done to stop getting these crap messages? Restart the server connection channel?
Thank you.
Last edited by mqwbiwf on Thu Oct 26, 2006 7:46 am; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Oct 26, 2006 7:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you just put the SVRCONN in a STOPPED state, you won't get these messages again... 
Or you could fix the application...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqwbiwf |
| Posted: Thu Oct 26, 2006 7:53 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
This is rather a serious issue, coz all the QMgr logs are getting filled up with these msgs which are of no use. And so we were not able to view some other important QMgr errors.
Jeff, what kind of fix should be taken in the application? I also saw somewhere that it might be due to PortScanner?? It would be greatly appreciated if you can provide me any feasible solution. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 26, 2006 8:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It could entirely be a PortScanner - if you've got one running tell it not to talk to the MQ Listener port.
The fix for the application is to just make sure that it disconnects properly all the time.
But if this is happening on a regular interval - every five minutes or etc. - then it's not likely to be the application. Apps shouldn't be disconnecting that often, much less disconnecting badly that often. It's a port scanner or a monitor tool trying to decide if MQ is running by using plain TCP.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqwbiwf |
| Posted: Thu Oct 26, 2006 8:11 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2006
Posts: 126
|
| Thanks for the info Jeff. We get hose messages very often (say every 3 mins). So it might be the Candle Monitoring tool that we have in place which might be checking if the ports are open, not sure though. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 26, 2006 8:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you think it *might* be a monitoring tool that is checking to see if Ports are open, then I guarantee it *is* the monitoring tool.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 26, 2006 3:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqwbiwf wrote: |
| Thanks for the info Jeff. We get hose messages very often (say every 3 mins). So it might be the Candle Monitoring tool that we have in place which might be checking if the ports are open, not sure though. |
Tell Candle to monitor MQ and not monitor the MQ ports through the OS!.. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rdubey |
| Posted: Thu Apr 26, 2007 6:09 am Post subject: |
|
|
Novice
Joined: 11 Jul 2006
Posts: 17
Location: USA
|
does anyone know why a port scanner would kill the listener . we had a similar problem where a 3-dns healthcheck is killing the listener . the telecom say
"The 3DNS servers send a SYN packet. If the MQ server answers with a SYN/ACK packet, the 3DNS server then sends a RST (reset) packet. This is called a tcp half open connection, because it does not complete a full 3way handshake" .
I think the runmqlsr should have handled the error and move on . |
|
| Back to top |
|
|
|
|
