|
Problem(Abstract) |
When trying to use monitoring policy for cluster members
does not work.
We need that when nodeagent starts it would start cluster member
application server if cluster has been started before nodeagent (or
machine where nodeagent and server are running) crashed.
We tried to set the "nodeRestartState" in server's monitoring policy to
"PREVIOUS" but it had no effect. Only when setting it to "RUNNING"
nodeagent started it automatically. But "RUNNING" is not good for us
because we do not want the nodeagent to start the server if the cluster
was in stopped state when nodeagent crashed. |
|
|
|
Cause |
The way node agent monitors app server is through a
monitor.state file (found in WAS_HOME/logs/nodeagent). Originally, node
agent only updated this file when the node agent process was being shut
down. So if the node agent crashed, it did not have a chance to execute
the shut down code, which would update the file. The monitor.state file
could be out-of-dated and when the node agent came back up, it would not
start all app servers that were previously running. |
|
|
Resolving the
problem |
The "Previous" state means after a node agent comes back
up, it is supposed to restore the app servers to its previous state. This
means the node agent would start the app server only if the app server was
running before the node agent process went down.
The way node agent monitors app server is through a monitor.state file
(found in WAS_HOME/logs/nodeagent). Originally, node agent only
updatedthis file when the node agent process was being shut down. So if
the node agent crashed, it did not have a chance to execute the shut down
code, which would update the file. The monitor.state file could be
out-of-dated and when the node agent came back up, it would not start all
app servers that were previously running.
We have decided to improve the code to better handle a crashed node
agent. PQ86894 has been opened for this. Currently there is a testfix on
PQ99999 for 5.1.0.x. --> This is an Internal IBM site. Also this fix
currently addrezsses the WAS 5.1.X, but you are at 5.0.2.x. This feature
will also be avail in WebSphere 5.0.2.7, which is expected to be realeased
end of June. Please let me know, if you will be more willing to apply WAS
5.0.2.7 or if you would prefer a test fix |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|