APAR status
Closed as program error.
Error description
When the nodeagent determines the app server is in a bad state
it will recycle the app server. If the app server takes too
long to stop the nodeagent will issue the start commands. The
start commands will fail and then the nodeagent will stop
helping the problem app. This fix will add a timer so the
nodeagent will check if the app server completes the stop before
issue the starts and failing.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Network *
* Deployment V5.0.2.x users who need node *
* agent to restart unreachable application *
* servers. *
****************************************************************
* PROBLEM DESCRIPTION: When node agent detects that an *
* application server is unreachable and *
* the application server has auto *
* restart set to true, node agent first *
* stops the unreachable application *
* server, then starts the application *
* server again. However, the node agent *
* does not wait for the application *
* server to completely stop before *
* issuing the start request. *
* *
* As a result, the application server *
* will fail to restart due to resources *
* (such as port) already in use problems. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Node agent did not check if the application server process has
ended before issuing a start request to start the application
server again. When the application server starts, the new
application server process attempts to allocate resources
such as ports, while the old application server process has
not finished releasing them. The new application server
process will fail because of this.
Problem conclusion
Improved the node agent code to check and only start the
unreachable application servers after the old process has gone
away. This ensures resources are released by the old process
and can be allocated by the new process being started.
This fix is scheduled for inclusion in 5.0.2.12. Please refer
to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg2700498
Temporary fix Comments
APAR information |
APAR number |
PK03782 |
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 |
2005-04-06 |
Closed date |
2005-05-09 |
Last modified date |
2005-05-09 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|