|
Problem(Abstract) |
Node agent does not work in WebSphere® Application Server
5.0. |
|
|
|
Resolving the
problem |
- Make sure the node agent is added to the Network Deployment Manager.
Open a console connected to the Network Deployment Manager and verify that
the node agent is in the System Administration > Node
Agent list. Also, check the icon in the Status column to see what the
Network Deployment Manager reports for the state of the specific node
agent.
- See if that node agent is running. Go to the machine that has the node
agent in question, WAS_HOME/AppServer/bin directory for that node,
and from a Windows® command prompt run serverstatus -all, or on
UNIX® ./serverstatus.sh -all. The output indicates what the machine
is running.
- If Steps 1 and 2 both state that the node agent is not started, but it
is added to the Network Deployment Manager, from a Windows command prompt
run startnode or on UNIX ./startnode.sh in the
WAS_HOME/AppServer/bin directory for that specific node.
- Verify that the ports are not in use by something else on the node
agent machine by issuing a netstat -an. Look for the ports that the
node agent uses.
- Open WAS_HOME/ND or Base/config/cells/Cell
Name/nodes/node name/serverindex.xml file.
- Search for nodeagent and you should find this xml tag:
<serverEntries...>.
- Between the <serverEntries...>. and </serverEntries> tags,
search the netstat output to verify that all the ports listed are open.
- If the problem is still not resolved, look at the stdout and stderr
logs for the node agent to see what they are stating. These files and
others for the node agent are located in the
WAS_HOME/AppServer/logs/nodeagent directory.
- If nothing else works call IBM support at 1-800-IBM-SERV.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|