Author |
Message
|
KAKOZ |
Posted: Wed May 19, 2004 4:34 am Post subject: MQS 5.3 - runmqlsr without specifying -p port param |
|
|
Voyager
Joined: 26 Jan 2004 Posts: 90 Location: FRANCE
|
Hi,
in the runmqlsr control commande it is said that if we dont specify the -p port param the default is that the listener will listen on the port defined in the TCP/IP qmgr definition
does that mean that if we have (on sun solaris box) for ex the /etc/services file like:
#
# mqseries
#
MQSeries 1414/tcp # MQSeries
MQSeries1 1415/tcp # MQSeries
MQSeries2 1416/tcp # MQSeries
MQSeries3 1417/tcp # MQSeries
if we start the listener with the command :
runmqlsr -t tcp -m qmgr_name
will the listener runmqlsr listen on all the ports 1414, 1415, 1416 and 1417 ??????
thanks for help
Jack |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 19, 2004 4:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
A listener only listens on one port - to the best of my knowledge.
But you could try it yourself and see. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mqonnet |
Posted: Wed May 19, 2004 4:56 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
I believe that etc/services is used only in conjunction with inetd.conf. If you manually start the listener with runmqlsr command then whatever port you specified is used. If none is specified runmqlsr would try and bind to the default port 1414.
If you are infact using inetd, then you have to have a definition looking like below.
MQSeries stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta -m qmgr_name
Take a look at the intercommunication manual. Explains this in detail.
Cheers
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
JasonE |
Posted: Wed May 19, 2004 5:28 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
I think you'll find we do a getservbyname(mqseries) for a tcp service, so in the example, only the 'mqseries' line is important. |
|
Back to top |
|
 |
KAKOZ |
Posted: Wed May 19, 2004 5:41 am Post subject: |
|
|
Voyager
Joined: 26 Jan 2004 Posts: 90 Location: FRANCE
|
Hi Jason,
It's not clear for me - using runmqlsr started for exemple as:
runmqlsr -t tcp
in the System Admin documentation (runmqlsr command) they say that:
<If you omit the port number, it is taken from the queue manager configuration information, or from defaults in the program.>
in that case where exactly is the "queue manager configuration" ? is it the
/etc/services files like:
MQSeries 1414/tcp # MQSeries
MQSeries1 1415/tcp # MQSeries
MQSeries2 1416/tcp # MQSeries
OR do we have to:
1- start all the listeners:
runmqlsr -t tcp -p 1414
runmqlsr -t tcp -p 1415
runmqlsr -t tcp -p 1416
then
2- NOTHING defined in the /etc/services file ????
thanks to clarify the pb
Jack |
|
Back to top |
|
 |
JasonE |
Posted: Wed May 19, 2004 6:55 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
I think if the /etc/services has
MQSeries 1414/tcp # MQSeries
MQSeries1 1415/tcp # MQSeries
MQSeries2 1416/tcp # MQSeries
then runmqlsr -t tcp will always use 1414.
If the line said
MQSeries 4444/tcp # MQSeries
then runmqlsr -t tcp will always use 4444
If you specify a port on the runmqlsr command, it will be used.
If you want multiple ports listened in I think you will need to run multiple listeners all with explicit ports |
|
Back to top |
|
 |
KAKOZ |
Posted: Wed May 19, 2004 7:02 am Post subject: |
|
|
Voyager
Joined: 26 Jan 2004 Posts: 90 Location: FRANCE
|
Jason
so if we want to use the default 1414 port we only have to:
1- start runmqlsr as
runmqlsr -t tcp (which takes 1414 by default)
and
2- nothing to code in the /etc/services file
we can also use:
runmqlsr -t tcp -p 1414 if we have to use only 1414
or
runmqlsr -t tcp -p 1414
runmqlsr -t tcp -p 1415
runmqlsr -t tcp -p 1416
and so on ...
if we have different port numbers to listen
and NOTHING to code in /etc/services (nor /etc/inetd.conf)
right ?
Jack |
|
Back to top |
|
 |
bower5932 |
Posted: Wed May 19, 2004 7:17 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
In the Systems Administration manual, there is a section on the queue manager configuration file. It has a TCP section which has a Port parameter. The default for this is 1414. I haven't tested this, but I would guess that if you have this parameter in your ini file, then this is what would get used by the runmqlsr command if you don't specify the '-p'. (There is even a comment in the runmqlsr command that indicates that it will use the configuration file value.)
The /etc/services is what gets used by amqcrsta and not runmqlsr.
If you want to listen on more than one port, then you'll need to start up another listener. |
|
Back to top |
|
 |
JasonE |
Posted: Wed May 19, 2004 7:51 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Hmmm - not my understanding nor my test results...
Nothing in \windows\system32\drivers\etc\services
start runmqlsr -m QM -t tcp
netstat shows listening on port 1414
Add "mqseries 9999/tcp" to etc\services
start runmqlsr -m QM -t tcp
netstat shows listening on port 9999 (well, actually on port 'mqseries', but a telnet to port 9999 shows thats the port its on) |
|
Back to top |
|
 |
bower5932 |
Posted: Wed May 19, 2004 7:54 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
Well, that is interesting. I wonder if the manual needs a little cleaning up? |
|
Back to top |
|
 |
JasonE |
Posted: Wed May 19, 2004 8:06 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
I couldnt comment
Of course, anyone is free to submit electronic readers comment forms  |
|
Back to top |
|
 |
any2xml |
Posted: Mon Jun 07, 2004 12:44 pm Post subject: runmqlsr - Default port |
|
|
Apprentice
Joined: 18 May 2004 Posts: 42
|
The default port for runmqlsr is 1414. It is best to specify the port. You can also listen on specific IP. For eg.
runmqlsr -p 1420 -i 125.36.45.24 -m MY.QUEUE.MANAGER
The documentation is fragmented and specific info about different platforms is mixed up.
One would think that runmqlsr would automatically work as a daemon. No, you need to use the '&' to run it in the background! _________________ A Perl Hacker
http://www.goreliance.com
http://www.any2xml.com |
|
Back to top |
|
 |
|