
Increase parallelism in CAA event handling

CAA can not start or stop resources. The resource move to the unknown state.
Also a core file is left behind by the action of starting and stopping
resources. The problem will occur after the first resource is started.

Enablers for Huron Packaged Database Solution

The datastore may get corrupted due to improper datastore locking. This may 
occur when multiple CAA CLI commands are run in the background.

caa_profile command may complain of failure to create and log EVM events.

The "caa_profile -create" command inserts extra attributes such as "REBALANCE"
into the profile when a user uses it to create an application profile.  This
will cause CAA GUI to fail to validate the profile.

The caa_stat command can crash, leaving a core file, when it receives a SIGPIPE
signal.  The problem has been known to occur when caa_stat output is piped to a
command such as "head".

When long resource or attribute names are used the space will not be reclaimed
correctly when the resource is unregistered.

Enabler for Huron Packaged Database Solution

Fix caad memory leak caused by caa_stat -f

CAA fails to close a TDF after processing a corresponding resource profile.
Over time this will lead to reaching the process limit for open file
descriptors and will prevent CAA from functioning properly.

clu_mibs agent has been changed to retry the connection with the Event Manager
daemon (evmd) indefinitely until it succeeds.
clu_mibs agent's start and stop control has been moved from
/sbin/init.d/clu_max script to /sbin/init.d/snmpd script.

This resolves erroneous behavior of resources with dependencies upon 
other resources (required resources). This solves several problems with 
starting, stopping, and relocating a resource with dependencies when the 
resource's start or stop scripts fail, or when relocating during a shutdown.

Enabler for Huron Packaged Database Solution

Enabler for Huron Packaged Database Solution.

The installation of this patch correctly migrates the old datastore to the
new datastore during the rolling upgrade and corrects the problem where no
resource information was preserved.
This patch resolves the issue with the default CAA system services (dhcp
named cluster_lockd autofs) not running after the installation of the patch
kit. In addition to the "default CAA system services" any previously registered
resource would be lost.

Prevents member hangs during boot in unusual circumstances that cause
the CAA daemon to crash or exit during initialization.

This patch fixes 3 CAA problems triggered by heavy CAA activity
conditions.

This patch fixes a problem in one of the shipped rc
scripts whereby Oracle will fail during start-up on
a clustered system.

This patch fixes the problem that App resource not going offline when last
dependent network resource goes OFFLINE.

This patch fixes a problem where CAAD might coredump due to a race condition
when multiple events to which it subscribes arrive simultaneously.

This patch fixes the problem when the target member crashes during service
start up.

This patch enables CAA to startup and failover system services before any
of the user services.


