|Applies To||RSA Product Set: Identity Governance and Lifecycle|
RSA Version/Condition: 7.0.1, 7.0.2
Product Description: RSA Identity Governance and Lifecycle
|Issue||Intermittently rules scheduled to run after Unification fail with the following exception in the aveksaServer.log (/home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log). Examples of rules that typically run after unification include but are not limited to Attribute Change Rules, Provisioning Joiner/Mover and Provisioning Termination Rules. Note that the actual rule name that fails may be different than what is shown in the example below.|
This may lead to other intermittent failures such as the failure to terminate users, or the failure to onboard new users from the rule.
|Cause||This issue may occur if the rule is executed against a partial set of data from a unification run. This may occur if the customer has scheduled collections or unification using the WebServices collectIdentities or Unify WebServices calls via a cron task or other scheduler in addition to running the collections manually or from the Collections Scheduling menu. |
The problem occurs if a new collection or unification is scheduled before the previous collection has completed. By design, rules configured to run after collections are scheduled at the time the collection is scheduled and they are placed in the scheduler queue so that they run after the unification step. If there are multiple unifications in the scheduler queue, the scheduled rule may run out of sequence and will not detect the changes from the unification run. When this occurs a NullPointerException is generated.
|Resolution||This issue has been resolved in the following versions.|
|Workaround||The following techniques may be used to avoid or mitigate the chances of a rule executing at the wrong time.|
|Notes||In all versions the default Scheduler under the Collectors tab in the Collectors Scheduling menu does not create a new daily, weekly or monthly collection until the original collection has completed. If a collection task is started manually, and the previous collection has not completed the system will prevent the collection from being scheduled and will display the following error:|