Node Agent failures

 

The Node Agent provides several important services to the Deployment Manger, appservers, and to the application clients. These services include administrative services, the Location Service Daemon, file transfer service, synchronization service, naming service, security service, and RAS service.

There are six types of errors in the process, network, disk, and machine that may cause a Node Agent server to fail: Expected server process failure, for example stopping the server. Unexpected server process failure, for example the server JVM crashes, simulated by kill -9. Server network problem, for example the network cable is disconnected or a router is broken. Unexpected and expected machine problems, for example a machine shutdown, operating system crashes, or power failures. Disk is faulty and the configuration file cannot be read. Overloading with heavy hacking or denial of service (DOS) attacks, simulated by continuously running wsadmin to the Node Agent using Mercury LoadRunner.

We discuss the behaviors of Node Agent server failures and how WebSphere V5 mitigates the impacts of these failures on WASs and application clients. Also, we describe how to set up Node Agents to tolerate these failures or to minimize the impact of these failures.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.