RippleStart combines stopping and starting operations. It
first stops and then restarts each member of the cluster. For example,
your cluster contains three cluster members named server_1, server_2 and
server_3. When you click RippleStart, server_1 stops and restarts, then
server_2 stops and restarts, and finally server_3 stops and restarts. Use
the RippleStart option instead of manually stopping and then restarting
all of the application servers in the cluster.
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
RippleStart specific MustGather information
- Stop all servers and clear the entire logs directory.
- Set tracing of the Admin component for the dmgr, nodeagent and all
cluster members for the cluster
- V5.0 =>
Admin=all=enabled:WLM*=all=enabled:Cluster*=all=enabled
- V6.0 =>
Admin=all:WLM*=all
- Make sure the trace output Maximum File Size limit is
large (20MB recommended) and Maximum Number of Historical Files is greater
than 5.
- See the appropriate Information
Center for additional information on tracing.
- Recreate the problem by issuing the RippleStart on the desired
Cluster.
- Run the Collector tool on all installs.
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to ripplestarts, search the WebSphere
Application Server support site.
|