| Author |
Message
|
| relheop |
 Posted: Fri Mar 05, 2004 3:34 am Post subject: listener Problem |
 |
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
| We have a big listener Problem with MQSeries v5.2 (Windows 2000). We have created one listener with port 1414, start as MQSeries-Service. Everything ok. .. 10 month later we saw in systemlog that this listerner want to start, but it can ´t start, because one was active with the same port. So we stop the MQSeries-service for this listener. The other one was active and worked. I want delete the listener, but I can ´t find the registry- or MQSeries entry. So we create a listener with port 1415. Months later we have the same problem with listener port 1415. What can we do to solve the problem? |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Fri Mar 05, 2004 5:28 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
How are you starting the listener ????
using MMC og by issuing runmqlsr parm.....
I've seen the problem when the listener wasn't stopped correctly, and after restart there might b esome running listeners.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Mar 05, 2004 5:39 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
There were a few 'features' of the MQ services when MQ lost the ability to track the process it launched, and hence reported the service as stopped or sometimes it tries to recover it (even though it was still running) causing in use errors - but if you looked in the task manager it was really running. This sounds the case for your problem - Always check the task manager to see if the process really is stopped or not.
Some cases of this were fixed in various fixpacks over time so also ensure your maintenance is kept up to date.
Of course, I'd also recommend you go to 5.3, ie a release which is in service... |
|
| Back to top |
|
|
| kman |
| Posted: Tue Mar 09, 2004 11:55 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Apart from using the latest version, I'd suggest that when you stop your queue manager, always opt to stop 'Normal'.
Stopping Immediate would leave something behind.. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Mar 10, 2004 3:30 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
It shouldnt for listeners as a stop is immediate from the service anyway (due to limited o/s time to allow the shutdown).
The other thing which casues this kind of thing is stopping the qmgr from the command line, as the service then knows nothing about it. Dont EVER mix command line and GUI unless you really understand what you are doing |
|
| Back to top |
|
|
| kman |
| Posted: Wed Mar 10, 2004 5:47 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Oh!. That's news to me. Thanks Jason. Before this, I did not care which way I use it, GUI nor Command Line. Which ever is within reach.
I'll remember to stick to doing things in the same way. |
|
| Back to top |
|
|
|
|
