Null pointer exceptions post 8.4 upgrade from 8.3

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

We recently upgraded to 8.4p2 from 8.3 post upgrade the system was stable for two days and all of a sudden we started experiencing null pointer exceptions for all refresh tasks, workflows and rules. Below is the error for a refresh task and the same error is for workflows too

An unexpected error occurred: The application script threw an exception: java.lang.NullPointerException BSF info: Rule-IdentityTrigger-AttributeSync at line: 0 column: columnNo

image
image1155×649 51.4 KB

Did anyone experience the same

2

Your best bet would be to examine the rule and the identities for which this is throwing NPE.

Enable debugging in the rule to gather more detail.

3

@AmruthaKallam can u post the rule here ?

Rule-IdentityTrigger-AttributeSync

5

Please see the code

<?xml version='1.0' encoding='UTF-8'?> This rule will be invoked when the IdentityEvent is fired from the Refresh. The log object associated with the SailPointContext. A sailpoint.api.SailPointContext object that can be used to query the database if necessary. The identity before the refresh/aggregation (this will be null when an identity is created). The identity after the refresh/aggregation (this will be null when an identity is deleted). A boolean describing the result of the rule. 
import sailpoint.rapidapponboarding.rule.AttributeSyncRuleLibrary;
// THIS  IS THE ENTRY POINT METHOD THAT IDENTITY TRIGGER CALLS WHEN INVOKED BY THE IDENTITY REFRESH
return AttributeSyncRuleLibrary.isEligibleForAttributeSync(context, previousIdentity, newIdentity,true);
6

I am suspecting previousIdentity should be null for some identity, please put trace and see.

7

This error is for all modification identities during aggregation or via workflow if a modification is requested for a user attributes in target application that requires refresh. Nothing more from logs. This had worked well before and suspecting if upgrade had changed anything.

8

Thank you for your responses. This issue is resolved. The root cause is identitfied as an application is corrupted during an upgrade and it needed to be removed and re-added. All the users with this applicatin association had failures. The error message is very generic though