| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| listener status Stopped |
« View previous topic :: View next topic » |
| Author |
Message
|
| pkbab |
 Posted: Sat Aug 08, 2009 3:49 am Post subject: listener status Stopped |
 |
|
Novice
Joined: 08 Aug 2009
Posts: 16
|
Hi All,
Environment: WebSphere MQ v7.0, Windows XP SP2.
I am new to WebSphere MQ an facing an issue while starting a listener using runmqlsr command.
Instead of using start listener command, I have used runmqlsr command to start a listener and after issuing command, status of listener is stopped. May I know the reason why listener was not started. |
|
| Back to top |
|
 |
| exerk |
| Posted: Sat Aug 08, 2009 4:01 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Do not use runmqlsr at this version, use a Listener object. Check the following:
1. Whether the queue manager has not already started a listener on the port you have specified in the command.
2. That the port you specified is not in use by another programme, or service.
3. Task Manager to see what runmqlsr processes are running.
NOTE: Duplicate post deleted.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| pkbab |
| Posted: Sat Aug 08, 2009 6:08 am Post subject: |
|
|
Novice
Joined: 08 Aug 2009
Posts: 16
|
Hi, Thanks for the reply and sorry for double posting.
| exerk wrote: |
| Do not use runmqlsr at this version, use a Listener object. |
May I know the reason why we should not use runmqlsr in wmq v7.0
| exerk wrote: |
1. Whether the queue manager has not already started a listener on the port you have specified in the command.
2. That the port you specified is not in use by another programme, or service.
3. Task Manager to see what runmqlsr processes are running.
|
1) I have monitored and observed that queue manager was already started and only one listener object was created on that particular queue manager.
2) No other application was using this port
3) Yes, have seen one runmqlsr process was running in task manager , but that process was running for the runmqlsr command issued by me.
May I know whether there is any alternate solution for tracing out this issue. |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Aug 08, 2009 9:01 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| pkbab wrote: |
| Hi, Thanks for the reply and sorry for double posting. |
No worries, sometimes it happens...
| pkbab wrote: |
| May I know the reason why we should not use runmqlsr in wmq v7.0 |
Since V6.0, listeners have been objects, and is the best practice way of controlling a listener. It also allows you to end a listener while the queue manager remains in a running state; and it's what runs in the background anyway.
| pkbab wrote: |
| 1) I have monitored and observed that queue manager was already started and only one listener object was created on that particular queue manager. |
And was that listener running?
| pkbab wrote: |
| 3) Yes, have seen one runmqlsr process was running in task manager , but that process was running for the runmqlsr command issued by me. |
Sure? If the queue manager is running, and its listener (as stated by you in 1) above) was running, which runmqslr process do you think was running?
| pkbab wrote: |
| May I know whether there is any alternate solution for tracing out this issue. |
Ensure that all listeners are ended, check no runmqlsr processes are running, then run the command line, check Task Manager for it, then try starting the listener defined in the queue manager, and check Task Manager again.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Aug 09, 2009 3:20 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| exerk wrote: |
| Do not use runmqlsr at this version, use a Listener object. |
Yeah, don't start the MQ listener by running a runmqslr command. Let the Queue Manager look after the MQ port listener by using a defined LISTENER type object. It still appears as a runmqlsr process.
Defining it is absurdly simple:
define listener('MY.LISTENER') trptype(TCP) port(1415) control(QMGR)
_________________
Glenn |
|
| 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
|
|
|
|
