| Author |
Message
|
| tanishka |
 Posted: Tue Dec 23, 2008 7:52 am Post subject: MQ version 5.3 and below versions: verify listener running |
 |
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| what is the command to know listener running or not on version 5.3 and below versions. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Dec 23, 2008 8:20 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Platform?
1. ps -fu mqm | grep "runmqlsr" for UNIX
2. MQSeries Services if Windows
_________________
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 |
|
|
| tanishka |
| Posted: Tue Dec 23, 2008 8:23 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
Platform LINUX and below is the output
ps -fu mqm | grep runmqlsr
mqm 7083 6197 0 10:59 pts/0 00:00:00 grep runmqlsr
[mqm@lxxxx mqm]$ ps -fu mqm | grep "runmqlsr"
mqm 7113 6197 0 11:00 pts/0 00:00:00 grep runmqlsr |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 23, 2008 8:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tanishka wrote: |
Platform LINUX and below is the output
ps -fu mqm | grep runmqlsr
mqm 7083 6197 0 10:59 pts/0 00:00:00 grep runmqlsr
[mqm@lxxxx mqm]$ ps -fu mqm | grep "runmqlsr"
mqm 7113 6197 0 11:00 pts/0 00:00:00 grep runmqlsr |
This is why I don't like the fu option. I am more partial to the ef option as the listener does not necessarily run under mqm. This has implications. A listener running under a different Id does not necessarily work as expected...
Note: you may not have a listener running.
| Code: |
| ps -ef | grep runmqlsr |
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tanishka |
| Posted: Tue Dec 23, 2008 9:00 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
same output
ps -ef | grep runmqlsr
mqm 9427 6197 0 11:59 pts/0 00:00:00 grep runmqlsr |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 23, 2008 9:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tanishka wrote: |
same output
ps -ef | grep runmqlsr
mqm 9427 6197 0 11:59 pts/0 00:00:00 grep runmqlsr |
So no listener running.
Remember to start it you have to finish the command line with '&' to put the listener into the background and run it as a daemon. You could possibly also try nohup.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Dec 23, 2008 2:56 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| fjb_saper wrote: |
| tanishka wrote: |
same output
ps -ef | grep runmqlsr
mqm 9427 6197 0 11:59 pts/0 00:00:00 grep runmqlsr |
So no listener running.
|
could still be running amqcrsta via inetd.conf...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 23, 2008 9:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Michael Dag wrote: |
| fjb_saper wrote: |
| tanishka wrote: |
same output
ps -ef | grep runmqlsr
mqm 9427 6197 0 11:59 pts/0 00:00:00 grep runmqlsr |
So no listener running.
|
could still be running amqcrsta via inetd.conf... |
Thanks for reminding me Michael. As I started working with MQ with 5.3 and runmqlsr I have a tendency to forget all the inetd setup.
Let's remind our friends out there that since version 5.3 IBM recommends the use of runmqlsr over the use of amqcrsta via inetd.conf.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
