| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CSS port tickling kills listener |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bill57 |
 Posted: Fri Nov 22, 2002 5:40 am Post subject: CSS port tickling kills listener |
 |
|
Apprentice
Joined: 26 Jul 2002
Posts: 35
Location: Atlanta, GA
|
I posted this yesterday and just realized I put it in the wrong forum..... sorry all. Anyway here it is again.
One of our sys admins recently fired up a script that ships with CSS (Cisco routers). I have not seen the script, but I understand it telnets to various ports to see if the service provided there is available. Well, we quicky discovered my MQ listeners don't like the protocol the scripts is using or something, they all came crashing down, and would not restart. Once the script was killed off, the listeners came back nicely.
Does anyone know more about what the listener is so sensitive to? I believe we can edit what is sent to the port at the hex level, so if I can figure out how to "tickle" the listener ports w/o killing the poor little guys off that would be nice!
Thanks
Bill
_________________
Bill Anderson
MQSeries Developer |
|
| Back to top |
|
 |
| jsware |
| Posted: Tue Nov 26, 2002 1:53 pm Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
Have a look in the errors directories to see what the listener doesn't like.
You'll find them in /var/mqm/errors, var/mqm/qmgrs/@SYSTEM/errors and /var/mqm/qmgrs/<your_qm_name>/errors.
You'll probably see some FDC files. The AMQERR*.LOG files should indicate which FDC file to look at.
Anyway - what version of MQ are you running on what platform? Do you have the latest CSD fixpack loaded. I know that MQ V5.2 had problems (memory leaks at least) with the runmqlsr program which were fixed in CSD04/05. I would recommend CSD05 on MQ5.2 (on NT & AIX at least).
If you telnet onto the port (telnet my_qm_hostname 1414) then you'll generally get disconnected. telnet does alot of terminal negotiation before you get to type anything which quite often causes the connection to get terminated. Are you sure it's telnet (with all the terminal negotiation) or are they doing a socket connect and then some send/recv calls?
I would not expect the listener to abend on you, just log errors that bad data was received. Maybe loading the latest CSD will fix the problem.
Cheers
John. |
|
| Back to top |
|
|
| Bill57 |
| Posted: Wed Nov 27, 2002 9:26 am Post subject: |
|
|
Apprentice
Joined: 26 Jul 2002
Posts: 35
Location: Atlanta, GA
|
This is WebSphere MQ 5.3 for AIX, there is no CSD out as yet that I am aware of. The error logs say "Incorrect data format received from host <hostname>. The FDC files show a major error code of xecE_W_UNEXPECTED_ASYNC_SIGNAL.
I found out the CSS script uses a polling mechanism called 'tcp', so, it may not be telnet negotiations causing the trouble.
_________________
Bill Anderson
MQSeries Developer |
|
| 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
|
|
|
|
