| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| start listener from command prompt |
« View previous topic :: View next topic » |
| Author |
Message
|
| rkford11 |
 Posted: Tue Dec 21, 2004 9:40 am Post subject: start listener from command prompt |
 |
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
Hi,
I am trying to run the listener from the command prompt.
Environment: windows 2000
MQ 5.3
i issue the MQSC command 'start listener' it gives me message saying
AMQ8021: Websphere MQ listener program started.
but when i go to MQ Services window the listener is not running.error log gives following message
AMQ9255: Listener already running.
EXPLANATION:
The request to start the WebSphere MQ listener failed because there is already
a listener running against the specified network resources.
i have tried changing the port number and issued the command but there's no change. please let me know where i am making the mistake. |
|
| Back to top |
|
 |
| clindsey |
| Posted: Tue Dec 21, 2004 9:48 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
From runmqsc, "start listener" can only start listener on the default port or 1414. It sounds like you already have a listener that is defined as a service so that it starts when the queue manager starts.
Starting it as a service is a good way to do it. If for some reason you do not want the listerner to start with the queue manager, go to MQ Services and undefine the listener. Then you can start it manually as needed from runmqsc.
If you just need to start a listener on a different port and it doesn't matter if it dies when you logoff, go to a command prompt and enter "runmqlsr -t tcp -m QMGRNAME -p PORT#
Charlie |
|
| Back to top |
|
|
| rkford11 |
| Posted: Tue Dec 21, 2004 10:20 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| clindsey wrote: |
From runmqsc, "start listener" can only start listener on the default port or 1414. It sounds like you already have a listener that is defined as a service so that it starts when the queue manager starts.
Starting it as a service is a good way to do it. If for some reason you do not want the listerner to start with the queue manager, go to MQ Services and undefine the listener. Then you can start it manually as needed from runmqsc.
If you just need to start a listener on a different port and it doesn't matter if it dies when you logoff, go to a command prompt and enter "runmqlsr -t tcp -m QMGRNAME -p PORT#
Charlie |
Actually i have created the listener using the following command in the script
amqmdain crtlsr QMGR -t tcp -p portnum
when i run the script the listener is created but not started. so how do i undeefine the listener so that i can start it using scripts.
Thanks |
|
| Back to top |
|
|
| clindsey |
| Posted: Tue Dec 21, 2004 12:41 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
amqdain doesn't give the granularity you need to set AUTO|MANUAL for individual services. You can only do it at the queue manager level. You will have to open the WebSphere MQ Services GUI and modify the listerner. You can set it to autostart. Then it will start when the queue manager starts. Also, you can undefine it from this GUI as well. From amqmdain, you can set the queue manager and all services to autostart with "amqmdain QMGR auto".
Charlie |
|
| 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
|
|
|
|
