PROBLEM: (92052, 94428) (PATCH ID: TCR540-021)
********
The problems addressed by this patch:
PROBLEM 1:
	whenever the REBALANCE attribute in the resource profile was blank, an 
attempt was made to remove the corresponding resource file in the clustercron
directory. This caused an error during a "caa_register -u"

PROBLEM 2:
	If a cluster member hosting an application resource panics while the      
resource is being stopped remotely(stop initiated from another cluster member), 
the resource remains inaccessible until the crashed member reboots and CAAD 
starts running on that member.


PROBLEM: (94304) (PATCH ID: TCR540-037)
********
PROBLEM: CAA core dumps trying to deal with cluster member id = 63.
	 The actual error ocurs when member ID 63 is the only cluster member
	 that is up. In this scenario, when resources try failing over to this
	 node, caad core dumps.


PROBLEM: (95782) (PATCH ID: TCR540-062)
********
PROBLEM:
CAAD might coredump due to a race condition when multiple events to which it
subscribes arrive at the same time when CAAD has not seen any events after
startup. This problem is seen mostly when the cluster loses Quorum due to a
member leaving the cluster.