APAR status
Closed as program error.
Error description
Application Server within a Network Deployment configuration
runs out of memory, this causes strange behavior in the
administration console. The console is unable to accurately
show the status of the application servers and performance
degrades rapidly.
Local fix
If able to find which Application Server has run out of memory
it can be killed and performance should improve.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server for Network *
* Deployment v5.x uesrs who have application *
* servers that would run out of memory. *
****************************************************************
* PROBLEM DESCRIPTION: When an application server runs out of *
* memory, node agent is not able to *
* administrate this application server *
* process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Node Agent has a thread that monitors the health of each
running application server. However, OutOfMemory error is
not caught by the monitoring thread.
Problem conclusion
Improved the node agent code to:
(1) attempt to catch the OutOfMemoryError originated from an
application server. The node agent will also try to stop the
app server process. If the app server has auto restart
enabled, the node agent will also try to restart the app
server next.
(2) display a message with the name of the app server that runs
into the OutOfMemoryError in the SystemOut.log of the node
agent. The message looks like:
An OutOfMemoryError occured on process: <application server
name>
Note:
If the problem app server is hung, the node agent may not be
able to stop its process. The process needs to be killed
manually.
Temporary fix
test fix available on
PQ99999 site, waiting for feedback
Comments
APAR information |
APAR number |
PQ85635 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-05 |
Closed date |
2004-07-12 |
Last modified date |
2004-07-12 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|