APAR status
Closed as program error.
Error description
1) Fix the sequence of stopNode -stopservers. Need to stop all
servers
first before stopping the node agent.
2) Record the server states before stopping the servers.
Local fix
none
Search Keywords: Monitor monitoring policy
Problem summary
****************************************************************
* USERS AFFECTED: Users who use the stopNode -stopservers *
* command with the setting of the server *
* restart state to "PREVIOUS" *
****************************************************************
* PROBLEM DESCRIPTION: When you set the server restart *
* state to "PREVIOUS" and call the *
* stopNode -stopservers command followed *
* by the startNode command, the *
* application servers will not be started *
* correctly according to their previous *
* states. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When calling stopNode -stopservers command, the node agent
is stopped first. This is not correect. It should stop
all application servers first and node agent at the end. All the
server states are not updated correctly after calling the
stopNode -stopservers command and it causes the "PREVIOUS"
server restart state to fail.
Problem conclusion
Fixed the server stopping sequence when calling stopNode
-stopservers command. All need to update the server states
correctly after stopping all servers and node agent.
Otherwise, the "PREVIOUS" restart server state function will
not work correctly after calling startNode.
The fix for this APAR is currently targeted for inclusion
in 5.02.12 and 5.1.1.5.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK02127 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-03-07 |
Closed date |
2005-05-09 |
Last modified date |
2006-02-15 |
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 NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|