| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Amqrmppa threads |
« View previous topic :: View next topic » |
| Author |
Message
|
| protocol |
 Posted: Thu May 01, 2008 10:59 am Post subject: Amqrmppa threads |
 |
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
I came across the below information:
"WebSphere MQ 5.3 removes the listener scalability problem once and for all. Rather than running each inbound connection as a thread within itself, runmqlsr now passes connections to one of the amqrmppa channel pooling processes. These amqrmppa's are threaded, but not massively so. This means they do not exhaust per-process resources or force administrators to increase maxuproc. The listener will start new amqrmppa processes as needed, so a single listener can now handle an unbounded number of connections. The listener is aware of the queue manager's status at all times, so it is also very quick to deny connections when the queue manager is down."
We plan to limit the number of amqrmppa processes from 64. But I dont understand what each thread under the amqrmppa process corresponds to. Is a thread opened per message or is it per channel connection. If it is per channel connection then does it mean that if we have 2 queue managers and 1 channel defined between them, the amqrmppa will always have just one thread?
I am confused, can someone clarify?
Thanks! |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu May 01, 2008 11:29 am Post subject: Re: Amqrmppa threads |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
One per channel.
| protocol wrote: |
| We plan to limit the number of amqrmppa processes from 64. |
Don't do that.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| protocol |
| Posted: Thu May 01, 2008 12:18 pm Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Peter,
Thanks for the immediate response!
This is the reason why we are trying to reduce the number of threads:
We are facing issues when suddenly some of the channels would start to go down one by one and we have to recycle the Queue Manger to get rid of this issue. This was happening in our production environment. Below is the exception we can see in the AMQERR logs when this happens:
"10/08/07 08:26:18
AMQ6037: WebSphere MQ was unable to obtain enough storage.
EXPLANATION:
The product is unable to obtain enough storage. The product's error recording routine may have been called.
ACTION:
Stop the product and restart it. If this does not resolve the problem see if a problem has been recorded. If a problem has been recorded, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
"
We feel this is happening as the mqm process has a memory limit of 256M and we are getting some very large messages through the channel. Reducing the number of threads would cause a new amqrmppa process to be spawned which would have a new 256M memory space and this issue would be avoided.
Is this a good approach?
[/b] |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
