| Author |
Message
|
| shruthi |
 Posted: Fri Apr 04, 2008 11:47 am Post subject: resource shortage prevented the creation of a WebSphere MQ p |
 |
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Hi Gurus,
we have more than 500 mq process and having resource shortage error as our max process for user is set to 500, we have the amqcrsta processess hanging from a year.
Q1> Why do we have the amqcrsta processess hanging , do we need to do some kind of setting.
Q2>Adding these parameters to qm.ini will help any
TuningParameters:
AgentClassMap=(1,1,1)
AgentClassLimit=(10,15,100) |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Apr 04, 2008 12:25 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You are incorrectly using inetd instead of runmqlsr. Do a search here for more details.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Apr 04, 2008 1:31 pm Post subject: Re: resource shortage prevented the creation of a WebSphere |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| shruthi wrote: |
Adding these parameters to qm.ini will help any
TuningParameters:
AgentClassMap...
AgentClassLimit... |
Did IBM support give you this information? If so, use it under the advice they gave. If not, I would ask for the reason why you are thinking of using these settings. They will not improve your experience of using amqcrsta processes. Thanks |
|
| Back to top |
|
|
| shruthi |
| Posted: Mon Apr 07, 2008 6:48 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Hi Mivic,
"TuningParameters:
AgentClassMap...
AgentClassLimit..."
it was not from IBM
After doing some google for out of resource i found adding those tuning parameters in qm.ini mayhelp but i was not sure whether that solves my problem. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 07, 2008 6:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| i was not sure whether that solves my problem. |
You'll have better luck changing from inetd to runmqlsr. Especially on more recent version of WMQ.
And if you're not on a recent version of WMQ, you should be.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Mon Apr 07, 2008 7:32 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| shruthi wrote: |
"TuningParameters:
AgentClassMap...
AgentClassLimit..."
it was not from IBM
After doing some google for out of resource i found adding those tuning parameters in qm.ini mayhelp but i was not sure whether that solves my problem. |
The parameters you mention do not affect channel behavior. Please delete this stanza to return to the original state of your qm.ini. |
|
| Back to top |
|
|
| shruthi |
| Posted: Mon Apr 07, 2008 8:28 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Hi Vitor/mvic
I didnot those parameters to qm.ini yet..
we are running our listeners in inetd.conf
Below are the line from inetd.conf
GB1 stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m QMGR_BROKER_1
we are using MQ 5.3 version |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 07, 2008 8:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
We repeat.
DO NOT USE INETD.
USE RUNMQLSR.
And, again.
Upgrade to v6. You're out of support and out of luck with MQ v5.3.
Unless you're running on NSK?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 07, 2008 12:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| we are running our listeners in inetd.conf |
Do not use inetd. Especially if you're having listener problems. There are improvements in runmqlsr.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
