Skip Headers
Oracle® Beehive Release Notes
Release 1 (1.5)

Part Number E14829-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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

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

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.

Known Issues in High Availability Environments

Ths section contains known issiues for Oracle Beehive deployments in high availability environments, and includes the following topic:

Oracle Beehive May Log "Multiple Connection" Warnings for Threads in High Availability Deployments with RAC Affinity Enabled

Bug 8290685. Oracle Beehive may log "multiple connection" warnings for threads in high availability deployments where RAC affinity is enabled. These warnings appear in OC4J logs and are attributed to Oracle Beehive services, such as the Time Management Service and the E-mail Service.