| Author |
Message
|
| csmith28 |
 Posted: Tue Jul 15, 2003 1:16 pm Post subject: resource shortage prevented the creation of MQSeries process |
 |
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
While stress testing an application on an AIX server running 4.3.3 with WebSphere 4 the app is failing and the WebSphere MQWorkflow and z8 Qmanager is throwing this alert to /var/mqm/errors/AMQERR01.LOG:
-------------------------------------------------------------------------------
07/14/03 13:59:31
AMQ6026: A resource shortage prevented the creation of an MQSeries process.
EXPLANATION:
An attempt to create an MQSeries process was rejected by the operating system
due to a process limit (either the number of processes for each user or the
total number of processes running system wide), or because the system does not
have the resources necessary to create another process.
ACTION:
Investigate whether a process limit is preventing the creation of the process
and if so why the system is constrained in this way. Consider raising this
limit or reducing the workload on the system.
-------------------------------------------------------------------------------
07/14/03 13:59:31
AMQ6184: An internal MQSeries error has occurred on queue manager OAX07P.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 20438.
ACTION:
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.
-------------------------------------------------------------------------------
It is also creating and FDC file with the following Probe ID: XC037008
The server CPU Usage was fine. Paging Space was fine, Memory Usage was acceptable.
I have also noticed that there are 65 amqzlaa0 processes running even though the aplication is now idle. No other appications reside on the server.
Shouldn't those processes go away after the SVRCONN channels go away?
Any help that you can provide would be appreciated.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Tue Jul 15, 2003 2:13 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Jul 15, 2003 2:58 pm Post subject: ver 5.2 |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Ver5.2 =[
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Jul 15, 2003 10:36 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| did you look at the page and enter the probe id? the first reference looks a lot like your symptom... |
|
| Back to top |
|
|
| csmith28 |
| Posted: Wed Jul 16, 2003 4:05 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Yes, I looked at the page. Now, is MAXUSERPROC a setting for MQSeries or is that the:
maxuproc 128 Maximum number of PROCESSES allowed per user True
setting that can be seen as part of the output from "lattr -El sys0" command.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jul 16, 2003 10:15 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| I think it is a system setting so not MQ |
|
| Back to top |
|
|
| rwa |
| Posted: Thu Jul 17, 2003 12:40 am Post subject: |
|
|
Voyager
Joined: 22 Jan 2002
Posts: 76
Location: Duesseldorf/Germany
|
I have seen this problem on Solaris 2.6 and Solaris 8 also. WSMQ needs some time to close open Channels. Also you can see an open socket (status: "time wait") for each amqzlaa0 process.
If you stop the activities after the error you will see the amqzlaa0 processes and open sockets disapearing.
My workaround was to reduce the connects/disconnects to WSMQ.
If you can not do this you have to increase the operating system settings like MAXUSERPROC, shared memory, etc. |
|
| Back to top |
|
|
|
|
