| Author |
Message
|
| jeevan |
 Posted: Tue Aug 20, 2013 6:41 am Post subject: netstat output on MQ server |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Hi Folks,
I have a question on netstat output on a MQ box
tcp4 0 0 127.0.0.1.4545 127.0.0.1.41553 ESTABLISHED
tcp 0 0 127.0.0.1.41553 127.0.0.1.4545 ESTABLISHED
tcp4 0 0 172.29.109.41.4545 172.29.109.41.51881 ESTABLISHED
tcp 0 0 172.29.109.41.51881 444.33.111.99.4545 ESTABLISHED
tcp4 0 0 444.33.111.99.4545 444.33.111.99.58621 ESTABLISHED
tcp 0 0 444.33.111.99.58621 444.33.111.99.4545 ESTABLISHED
tcp4 0 0 444.33.111.99.4545 444.33.111.99.35005 ESTABLISHED
tcp 0 0 444.33.111.99.35005 444.33.111.99.4545 ESTABLISHED
tcp4 0 0 127.0.0.1.4545 127.0.0.1.50203 ESTABLISHED
tcp 0 0 127.0.0.1.50203 127.0.0.1.4545 ESTABLISHED
tcp4 0 0 127.0.0.1.4545 127.0.0.1.51401 ESTABLISHED
tcp 0 0 127.0.0.1.51401 127.0.0.1.4545 ESTABLISHED
What we can see in the above list is that a process from loopback ip makes connection itself.
originates from the mq listener port(4545) and makes connection to other port eg 51401
originates from other port (50203) and makes connection to listener port 4545
also makes similar connection from real ip
how should I intepret this ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 20, 2013 6:44 am Post subject: Re: netstat output on MQ server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jeevan wrote: |
| how should I intepret this ? |
As a series of connections?
I don't understand what you're asking, or why.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Aug 20, 2013 6:50 am Post subject: Re: netstat output on MQ server |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Vitor wrote: |
| jeevan wrote: |
| how should I intepret this ? |
As a series of connections?
I don't understand what you're asking, or why. |
basically, the connection should be from local to foreigh ip and viceversa corect
but what i am seeig is
(1) from local loopback ip to loopback ip from and to the port mq is listening,
(2) from local ip ( not loopback, correct ip) to correct ip from and to the port Mq is listening
In fact I am working to dismantle a very old qmgr, so I am trying to see wha are connected to but I but I see a local to local connection.
Last edited by jeevan on Tue Aug 20, 2013 6:58 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 20, 2013 6:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Have you determined that any of these are applicable to mq processes? |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Aug 20, 2013 7:07 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mqjeff wrote: |
| Have you determined that any of these are applicable to mq processes? |
When I get lsof -i :port I can see the amqrmppa process listening to the port.
Why a channel process is listening to the local loopback ip? also why the connection request comes from local to local |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Aug 20, 2013 3:11 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| jeevan wrote: |
| When I get lsof -i :port I can see the amqrmppa process listening to the port. |
The process is not "listening" on the port, it has an established socket session open, and could be reading or writing.
| Quote: |
| Why a channel process is listening to the local loopback ip? also why the connection request comes from local to local |
Local MQ Client applications are probably connected to the local queue manager. Compare netstatus to runmqsc "dis chs(*) current all".
_________________
Glenn |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Aug 22, 2013 10:08 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| gbaddeley wrote: |
| jeevan wrote: |
| When I get lsof -i :port I can see the amqrmppa process listening to the port. |
The process is not "listening" on the port, it has an established socket session open, and could be reading or writing.
| Quote: |
| Why a channel process is listening to the local loopback ip? also why the connection request comes from local to local |
Local MQ Client applications are probably connected to the local queue manager. Compare netstatus to runmqsc "dis chs(*) current all". |
Thanks for reminding me. I was only talking for the last oe year and my MQ skill which gives me bread and butter, nearly get expired. I am renewing it.
thanks a lot |
|
| Back to top |
|
|
| Tibor |
| Posted: Fri Aug 23, 2013 1:04 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| jeevan wrote: |
| When I get lsof -i :port I can see the amqrmppa process listening to the port. |
MQ listener process (runmqlsr) is *really* listening on the port (sorry gbaddeley), and this process launches the pooling processes (amqrmppa).
| Quote: |
| Why a channel process is listening to the local loopback ip? also why the connection request comes from local to local |
You can set which interface is using for a listener, all is the default. Besides, a local-to-local scenario is very common, because it is flexible and portable. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Aug 25, 2013 4:30 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Tibor wrote: |
| MQ listener process (runmqlsr) is *really* listening on the port (sorry gbaddeley), and this process launches the pooling processes (amqrmppa). |
To be pedantic, at least one amqrmppa process is already running. The listener hands over the channel connection to a spawned thread in amqrmppa. Each instance of amqrmppa can have up to ~60 threads acting as Message Channel Agents.
_________________
Glenn |
|
| Back to top |
|
|
| Tibor |
| Posted: Sun Aug 25, 2013 8:57 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
|
| Back to top |
|
|
|
|
