| Author |
Message
|
| Inforz |
 Posted: Mon Mar 11, 2013 10:50 am Post subject: Identifying amqrmppa process |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
Hi,
its windows environment
I have a queue's ipprocs count to be 1 which is said it to be amqrmppa process(channel process pooling job) when viewed through queue's status. (I even got the process id)
Actually saying I couldnt understand this amqrmppa. Anyways my need is to know which channel/program is inquiring this queue and need to know more info about it. Please help me |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 11, 2013 11:05 am Post subject: Re: Identifying amqrmppa process |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| Actually saying I couldnt understand this amqrmppa. Anyways my need is to know which channel/program is inquiring this queue and need to know more info about it. |
You said yourself; it's the channel pooling job as described here and here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 11, 2013 11:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
also, "ipprocs" doesn't have anything to do with inquiry.
The only way the channel pooling process should be reading this queue is if it's an XMITQ. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Mar 11, 2013 5:11 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
An instance of a SVRCONN channel driven by an MQ Client app can have a local non XMITQ queue show IPROCS> 0 by amqrmppa.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Mar 12, 2013 3:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| An instance of a SVRCONN channel driven by an MQ Client app can have a local non XMITQ queue show IPROCS> 0 by amqrmppa. |
really? interesting. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Mar 12, 2013 4:15 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| mqjeff wrote: |
| PeterPotkay wrote: |
| An instance of a SVRCONN channel driven by an MQ Client app can have a local non XMITQ queue show IPROCS> 0 by amqrmppa. |
really? interesting. |
OK...when I issue the Q Usage command on a Local Q opened by amqsputc, it shows amqsputc as having the q open. But isn't it really the amqrmppa process that owns the thread that represents this client connection that actually has the q open? I realize its more useful to see that its an instance of amqsputc that has the q open....
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Mar 12, 2013 4:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| mqjeff wrote: |
| PeterPotkay wrote: |
| An instance of a SVRCONN channel driven by an MQ Client app can have a local non XMITQ queue show IPROCS> 0 by amqrmppa. |
really? interesting. |
OK...when I issue the Q Usage command on a Local Q opened by amqsputc, it shows amqsputc as having the q open. But isn't it really the amqrmppa process that owns the thread that represents this client connection that actually has the q open? I realize its more useful to see that its an instance of amqsputc that has the q open.... |
Well, the other thing is that SVRCONNs don't use the same transport protocol to talk to CLNTCONNS that other MQ channels use to talk to each other.
So the MCA is going to do different things, which means it may not be using threads under amqrmppa.
But, really, I don't know. I've not sat down and monitored MQ at this level in a while. So it's interesting. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Mar 12, 2013 4:09 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| PeterPotkay wrote: |
| ... But isn't it really the amqrmppa process that owns the thread that represents this client connection that actually has the q open?... |
Yes. The amqrmppa thread makes MQI calls on behalf of the client app, and invokes exit points if they are defined on the SVRCONN. The channel status shows the name of the client app process, not amqrmppa.
_________________
Glenn |
|
| Back to top |
|
|
|
|
