| Author |
Message
|
| mrlinux |
 Posted: Thu Sep 04, 2003 7:21 am Post subject: |
 |
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
have you tried runmqlsr, then have inetd try to start a listener and see what error it generates ???
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
 |
| skn |
| Posted: Thu Sep 04, 2003 7:22 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
ok take a look at this
mqm 23789 270 0 Aug 31 ? 0:00 amqcrsta -m XXX
mqm 8472 270 0 Sep 03 ? 0:01 amqcrsta -m XXX
mqm 23179 270 0 Aug 31 ? 0:00 amqcrsta -m XXX
mqm 15397 270 0 11:42:37 ? 0:00 amqcrsta -m XXX
mqm 6676 270 0 Aug 27 ? 0:00 amqcrsta -m XXX
mqm 21182 270 0 09:29:32 ? 0:00 amqcrsta -m XXX
mqm 6675 270 0 Aug 27 ? 0:00 amqcrsta -m XXX
mqm 15398 270 0 11:42:37 ? 0:00 amqcrsta -m XXX
mqm 20510 270 0 Sep 02 ? 0:06 amqcrsta -m XXX
mqm 25484 1 0 Aug 05 ? 0:00 runmqlsr -m XXX -t tcp -p 1415 |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Sep 04, 2003 7:37 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Are you trying to say that both the inetd listener and runmqlsr are staying up without producing any errors.
You sure both the amqcrsta processes listed and the runmqlsr are for the same QMGR. Are they configured for the same port?
Is there any reason why you want to run both inetd and runmqlsr?
If you want to use runmqlsr, then kill inetd daemon and remove the entries in inetd.conf and restart inetd daemon. Now start the listener using runmqlsr. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Sep 04, 2003 7:56 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
You need to pick either runmqlsr or inetd.conf to run the listener otherwise you will get errors
The following indicates a client that did not disconnect properly or is still connected after a week, note the date
mqm 6676 270 0 Aug 27 ? 0:00 amqcrsta -m XXX
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| skn |
| Posted: Thu Sep 04, 2003 8:12 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
i just checked the amqcrsta and runmqlsr and none of them are on the same port.Thats fine.but all the qmanagers are listed in the inetd.conf file with corresponding ports in services.And i can see the runmqlsr threads for all the qmgrs.
Now i am not entirely sure if the inetd file has been refreshed (cant get hold of my unix admin) but i am assuming so since its been added back in 2002.
What i am trying to figure out is , whether the error logs about the listener ( take a look at the beginning of this thread) have anything to do with the fact that the listeners are being run as threads in spite of being listed as services.If not what are other possible reasons for the listener error logs. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Sep 04, 2003 10:30 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Do the port numbers runmqlsr uses the same as the ones in the /etc/services file ???? if so then you have an issue
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| skn |
| Posted: Thu Sep 04, 2003 10:41 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Sep 04, 2003 11:18 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well you need to stop one of them, my recommedation is to discontiue using runmqlsr. However IBM's Recommondation is just the oppsite.
Choose one but not both.
My reason for recommending it is, if one amqcrsta process dies it doesnt
stop all the channels such as if runmqlsr dies. also runmqlsr is threaded
and if dont have your max threads bump up in the kernel then you could
end up hitting that.
IBM's reason is that it is threaded and performs better because of it.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
