Author |
Message
|
morpheus |
Posted: Tue Aug 26, 2003 8:05 am Post subject: using runmqlsr and inetd.conf |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
Hi All,
I found out runmqlsr processes and entries in inetd.conf file for the same queue managers in one of our SunSolaris machine. Is it ok to have both. The reason I'm asking this question is we are getting AMQ9209 error messages in the logs. Everything works fine but I don't understand why I'm getting this message.
----------------------------------------------------------------------------
08/21/03 15:41:54
AMQ9209: Connection to host 'name (xxx.xx.xx.xx)' closed.
EXPLANATION:
An error occurred receiving data from 'name (xxx.xx.xx.xx)' over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
-------------------------------------------------------------------------------
Is it because of the listener - inetd.config conflict or is it someother issue.
Please provide me with some insight about this
Thank you
-Morpheus |
|
Back to top |
|
 |
vennela |
Posted: Tue Aug 26, 2003 8:52 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Though you have entries in inetd.conf file, I don't think they are being used. Because, if that's the case then the listener should not stay up, because the port is already being used.
The above errors I think are not the outcome of what you have mentioned.
-------
Venny |
|
Back to top |
|
 |
morpheus |
Posted: Wed Aug 27, 2003 4:42 am Post subject: Thank you |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
Then, do you have any idea why I'm getting this error?
I could ping the host and all the channels & listener working. I don't know why I'm getting this error. |
|
Back to top |
|
 |
vennela |
Posted: Wed Aug 27, 2003 6:31 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Are you getting this problem regularly or is it a one time problem.
It could be because of some network glitch. |
|
Back to top |
|
 |
morpheus |
Posted: Wed Aug 27, 2003 6:42 am Post subject: |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
I'm getting this message for every 15 seconds.
My error logs are being filled up with these messages. |
|
Back to top |
|
 |
Toronto_MQ |
Posted: Wed Aug 27, 2003 7:07 am Post subject: |
|
|
 Master
Joined: 10 Jul 2002 Posts: 263 Location: read my name
|
This message is often produced in the qmgr error logs if a client which is connected to the qmgr doesn't do a proper MQDISC.
Steve |
|
Back to top |
|
 |
bower5932 |
Posted: Wed Aug 27, 2003 10:46 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
If you have both inetd and runmqlsr using the same port, I'd switch one of them. I don't know if it is causing this problem, but I wouldn't think that it could be good. |
|
Back to top |
|
 |
Anirud |
Posted: Sat Oct 09, 2004 3:42 pm Post subject: |
|
|
 Master
Joined: 12 Feb 2004 Posts: 285 Location: Vermont
|
morpheus,
How did you get this problem solved? I am getting this error too ( on more that one queue managers).
I came to a conclusion after searching for a while on this issue that there might be 2 possible reasons for this error.
1) port scanning tool
2) without proper MQDISC.
I don't have a port scanning tool.
I would appreciate if you could let me know what was the cause in your case. |
|
Back to top |
|
 |
Manikandan |
Posted: Sun Oct 10, 2004 10:04 pm Post subject: |
|
|
Voyager
Joined: 07 Jul 2004 Posts: 78
|
Get a tool like lsof to find whether the port is already used or the port is used by this listener.
lsof can be got from
www.sunfreeware.com |
|
Back to top |
|
 |
|