| Author |
Message
|
| WBI_user |
 Posted: Fri Jun 17, 2005 6:26 am Post subject: MQ listener on Linux not started by xinetd |
 |
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
I tried to start a channel from a V53 Qmgr on Winxp to a v53 qmgr on Red Hat 9 linux. Channel went intoi retry. I found that this was because the listener was not running on RH9 Linux.
I did a runmqlsr -m LINUXQM -t TCP -p 1414 on Linux and the channel started ok.
But I have done everything according to the Intercommunication manaul to use xinetd. Just don't know why it is not working
Here is my set up
In "etc/services" I have
# Local services
MQSeries 1414/tcp #LINUXQM
In "etc/xinetd.d/MQSeries" I have
# WebSphere MQ service for XINETD
service MQSeries
{
disable = no
flags = REUSE
socket_type = stream
wait = no
user = mqm
server = /opt/mqm/bin/amqcrsta
server_args = -m LINUXQM
log_on_failure += USERID
}
I always restart xinetd just to be sure, but I don't see the listener
[root@RH9 root]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
[root@RH9 root]#
[root@RH9 root]# netstat -l | grep MQ
[root@RH9 root]# netstat -l | grep 1414
[root@RH9 root]# chkconfig MQSeries on
[root@RH9 root]# netstat -l | grep 1414
[root@RH9 root]# netstat -l | grep MQ
[root@RH9 root]#
[root@RH9 root]# netstat -an | grep MQ
[root@RH9 root]# netstat -an | grep 14
[root@RH9 root]#
you can see that nothing returns on netstat
If I started the listener myself
runmqlsr -m LINUXQM -t TCP -p 1414
then netstat will show
[root@RH9 root]# netstat -an | grep 14
tcp 0 0 0.0.0.0:1414 0.0.0.0:* LISTEN
I have also tried to put "port = 1414" in "xinetd.d/MQSeries" and also tried to change user from mqm to root in "xinetd.d/MQSeries" with no luck.
Any suggestion ? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jun 17, 2005 6:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Using runmqlsr is the recommended approach.
It's no harder to add an entry to /etc/rc.local than it is to add an entry to /etc/xinetd.d/
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| malammik |
| Posted: Fri Jun 17, 2005 7:02 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| WBI_user |
| Posted: Fri Jun 17, 2005 9:42 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
Thanks for the hint malammik, xinetd -d shows that it has error parsing the MQSeries file in xinetd.d. The file was created using gedit 2.2.0 in my RH9 system. I had problem with notepad before which can cause problem with unseen character being introduced.
I deleted /etc/xinetd.d/MQSeries and recreate it using vi editor. Now xinetd -d shows no problem and netstat shows port 1414 in listen status.
But my channel still go into retry status.
If I stop xinet for MQSeries and run the listener myself. It works. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jun 17, 2005 9:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| WBI_user wrote: |
| If I stop xinet for MQSeries and run the listener myself. It works. |
Then use it! Stop trying to troubleshoot a problem that you don't need to troubleshoot - particularly for a less supported less recommended approach to running listeners.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| WBI_user |
| Posted: Fri Jun 17, 2005 11:07 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
jefflowrey, I understand what you mean. But I think we learn a lot through trouble shooting. Not just MQ but also the environment. I had it working with runmqlsr before I posted my question. Now I understand more about how xinetd works through this exercise and I learned not to use the editor.
Since I have xinetd running fine now on Linux. But it is still retrying, there must be something different between using xinetd and runmqlsr. I am hopeing to learn more about Linux through this exercise. |
|
| Back to top |
|
|
| WBI_user |
| Posted: Fri Jun 17, 2005 11:25 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
Hi jefflowrey, just for learning purpose also why do you say inetd is the
"less supported less recommended approach to running listeners."
I have searched through the IBM manuals and did not find any recommnedation on using runmqlsr over inetd ( or xinetd). A pointer to any documentation will be greatly appreciated. We all want to learn the best practice. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jun 17, 2005 11:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Just for learning purposes, the reasons to use runmqlsr instead of xinetd are spelled out in a large number of different posts here.
There is a button marked "search". It should be a good learning exercise to find this information yourself.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| malammik |
| Posted: Fri Jun 17, 2005 11:37 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| bbburson |
| Posted: Fri Jun 17, 2005 12:52 pm Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 17, 2005 5:12 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
|
|
