5 High Availability Notes

This module contains the following type of information regarding Oracle Beehive deployments in high availability environments:

• Known Limitations and Workarounds in High Availability Environments

Known Limitations and Workarounds in High Availability Environments

This section contains known limitations and workarounds for Oracle Beehive deployments in high availability environments, and includes the following topic:

• High Availability Deployments Configured to Use SSL May Experience False ONS Notification Errors

High Availability Deployments Configured to Use SSL May Experience False ONS Notification Errors

Bugs 6692689 and 6978935. Oracle Beehive deployments in high availability environments that are configured to use SSL may experience false ONS notification errors, similar to the following:

ons notification handler failed [[Java.lang.NullPointerException]]

If these errors occur, they should be ignored. Entries for occurrences of these errors will appear in one or more of the system's log files, such as BEEAPP_log.txt, BEECORE_log.txt, and BEEMGMT_log.txt.

BEEAPP OC4J Failures May Cause Some XMPP Clients to Experience Delays Upon Reconnection

Bug 7041499. If one or more BEEAPP OC4J instances fail, users of XMPP clients may experience initial delays of up to several minutes when reconnecting to the system. This includes deployments that have multiple Oracle Beehive Application Tier instances or that have multiple instances of the BEEAPP OC4J. This issue occurs in cases where a user's roster was maintained in the cache of a failed node but not in the surviving nodes. The delay occurs until the system can restore the user's roster in the surviving nodes, which typically takes several minutes or less.