2.8.5 Troubleshooting

A few troubleshooting tips: - The easiest part to misconfigure for backup clusters is the core group bridge. There are several settings that must be entered from the other cluster. To review all of the core group bridge settings at once, go to Servers  | Core group bridge settings. Expand the DefaultAccessPointGroup and all items below to see the group names, host names, and ports. Compare the primary cell and backup cell to cross check that the access point group from one matches information in the peer access group of the other.

- Review the backup cluster settings for the correct host name and bootstrap address on both the primary and backup cell. Double check that the cluster names are identical.

- Verify that the application is correctly mirrored on the backup cluster. You might need to set up the same resources with the same settings and install the same application (or mirrored resources if the same database will not be used).

- Check that the application works in a non failover mode on both the primary and backup cells.

- Check that the machines in the cells can all contact each other. If they are separated by firewalls, verify that the WebSphere related ports are opened.

- When the primary EJB cluster is down, try accessing the EJBs with a new client or new browser. New connections have the information to connect to the backup cluster.

ibm.com/redbooks

Next