Null pointer exception error

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.2

Please share any other relevant files that may be required (for example, logs).

Screenshot 2024-06-24 181407.png
Screenshot 2024-06-24 181407.png1280×398 28.8 KB

Share all details related to your problem, including any error messages you may have received.

Hi All,

Few days back we have enabled “Rapidsetup leaver” in our SailPoint production environment, and we have started getting error of null pointer exception from our refresh task, Perform identity request maintenance task and most importantly successfactor aggregation task as well which is a authoritative source

2

hi @ayadav_12 ,

It will be difficult to identify with just this screenshot. Can you share more details.
May be you can check if it is also happening in lower environment.
Run one aggregation at a time and check the loggers by enabling logger statments.

Thanks,
Uday

3

Hi @ayadav_12,

maybe in one(or more) rule of leaver process dont check if a variable is distinct of null.
Can you share the log trace of those error? you can find in catalina.out or in another file if its configured

4

Hi @ayadav_12 ,

From the screenshot, it does say that there is a null pointer exception in your leaver identityTrigger rule Orbia-LeaverSendEmailNotification-IdentityTrigger.

Please check if any variables are not handled properly, you can post the related code, such that we can help you out too.

Regards,
Uday Kilambi

5

Hi @ayadav_12 ,

Yes I agree with @uday_kilambiCTS , please enable extended logging in the trigger and verify through it.

Thanks,
Kavindar Sharma

1 Like
6

Hi @ayadav_12,

Along with above suggestion try to add below snippet in the log and see which specific part is throwing error and share the same for more help.

<Variable initializer="true" name="trace"/>

Thanks

7

Hi @ayadav_12,
In addition to all the above that are suggested.
Please check which option of identity refresh is causing this null pointer exception

Is it because of refresh identity attributes/ synchronise attributes/ refresh roles detected assigned / provision assignments

Based on that option you need to check if any errors in provisioning transactions for a particular application (check null pointer exception code)

Enable loggers for identity refresh to see more details on the error and take action accordingly

Regarding aggregation errors you need to add null checks in your logic. Is it data issue at target that you have not handled.

8

Hi All,

Below is the stacktrace of the error we are receiving for null pointer exception. How we can rectify which user causing these issues.
2024-06-24T02:48:30,548 ERROR Thread-26286 org.hibernate.internal.ExceptionMapperStandardImpl:39 - HHH000346: Error during managed flush [deleted object would be re-saved by cascade (remove deleted object from associations): [sailpoint.object.EntitlementGroup#ac10261b902b1b2c81903119a2ce4085]]
2024-06-24T02:48:30,548 ERROR Thread-26286 sailpoint.task.IdentityRefreshExecutor:1358 - Unable to release lock
2024-06-24T02:48:30,564 ERROR Thread-26286 sailpoint.task.IdentityRefreshExecutor:1359 - sailpoint.tools.GeneralException: deleted object would be re-saved by cascade (remove deleted object from associations): [sailpoint.object.EntitlementGroup#ac10261b902b1b2c81903119a2ce4085]
2024-06-24T02:48:30,580 ERROR Thread-26286 sailpoint.task.IdentityRefreshExecutor:1360 - Decache and try again
2024-06-24T02:48:30,611 ERROR Thread-26286 sailpoint.task.IdentityRefreshExecutor:1624 - RefreshWorker 1 exception: null
java.lang.NullPointerException: null
at sailpoint.persistence.ClassPersistenceManager.getManager(ClassPersistenceManager.java:162) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.persistence.ClassPersistenceManager.removeObject(ClassPersistenceManager.java:296) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.server.InternalContext.removeObject(InternalContext.java:834) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.api.EntitlementCorrelator.saveDetectionAnalysis(EntitlementCorrelator.java:1086) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.api.Identitizer.refresh(Identitizer.java:2388) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.task.IdentityRefreshExecutor$RefreshWorker.refreshAndProcess(IdentityRefreshExecutor.java:1585) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.task.IdentityRefreshExecutor$RefreshWorkerPool.queue(IdentityRefreshExecutor.java:1903) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.IdentityRefreshRequestExecutor.refresh(IdentityRefreshRequestExecutor.java:487) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.IdentityRefreshRequestExecutor.execute(IdentityRefreshRequestExecutor.java:209) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.RequestHandler.run(RequestHandler.java:163) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]

Regards
Amit

9

I think you have an association with a deleted object on an identity.
In this case you have the entitlement with id [ac10261b902b1b2c81903119a2ce4085] assigned on an identity but this entitlement dont exist.

You can try to find it on DB and clear or search in IIQ and delete from debug.

If find this topic with attached rule, maybe it can help you

3 Likes
10

Hi @enistri_devo ,

I ran this rule last friday and it worked successfully till yet. Currently we are facing some errors in the refresh tasks as mentioned below:
2024-08-26T06:18:59,054 WARN Thread-84809 engine.jdbc.spi.SqlExceptionHelper:137 - SQL Error: 1205, SQLState: 40001
2024-08-26T06:18:59,054 ERROR Thread-84809 engine.jdbc.spi.SqlExceptionHelper:142 - Lock wait timeout exceeded; try restarting transaction
2024-08-26T06:18:59,054 ERROR Thread-84809 sailpoint.request.RequestProcessor:1688 - Unable to update shared TaskResult for Request
2024-08-26T06:18:59,054 ERROR Thread-84809 sailpoint.request.RequestProcessor:1689 - sailpoint.tools.GeneralException: could not extract ResultSet
2024-08-26T06:19:00,054 WARN Thread-84813 engine.jdbc.spi.SqlExceptionHelper:137 - SQL Error: 1205, SQLState: 40001
2024-08-26T06:19:00,054 ERROR Thread-84813 engine.jdbc.spi.SqlExceptionHelper:142 - Lock wait timeout exceeded; try restarting transaction
2024-08-26T06:19:00,054 ERROR Thread-84813 org.hibernate.internal.ExceptionMapperStandardImpl:39 - HHH000346: Error during managed flush [could not execute statement]
2024-08-26T06:19:00,054 WARN Thread-84813 sailpoint.task.TaskMonitor:289 - Error updating task progress. sailpoint.tools.GeneralException: could not execute statement
2024-08-26T06:19:00,054 ERROR Thread-84813 sailpoint.task.IdentityRefreshExecutor:1624 - RefreshWorker 1 exception: failed to lazily initialize a collection of role: sailpoint.object.Identity.assignedRoles, could not initialize proxy - no Session
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.Identity.assignedRoles, could not initialize proxy - no Session
at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:597) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:216) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:576) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:147) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.collection.internal.PersistentList.iterator(PersistentList.java:155) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at sailpoint.tools.xml.ReferenceListSerializer.serializeToElement(ReferenceListSerializer.java:49) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.tools.xml.AnnotationSerializer.serializeToElement(AnnotationSerializer.java:557) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.tools.xml.XMLObjectFactory.toXml(XMLObjectFactory.java:301) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.tools.xml.XMLObjectFactory.toXml(XMLObjectFactory.java:271) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.tools.xml.XMLObjectFactory.toXml(XMLObjectFactory.java:249) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.tools.xml.XMLObjectFactory.clone(XMLObjectFactory.java:387) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.object.SailPointObject.deepCopy(SailPointObject.java:1452) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.api.Identitizer.loadPreviousIfRequired(Identitizer.java:3150) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.api.Identitizer.refresh(Identitizer.java:2270) ~[identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.task.IdentityRefreshExecutor$RefreshWorker.refreshAndProcess(IdentityRefreshExecutor.java:1585) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.task.IdentityRefreshExecutor$RefreshWorkerPool.queue(IdentityRefreshExecutor.java:1903) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.IdentityRefreshRequestExecutor.processEventsOnly(IdentityRefreshRequestExecutor.java:288) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.IdentityRefreshRequestExecutor.execute(IdentityRefreshRequestExecutor.java:215) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
at sailpoint.request.RequestHandler.run(RequestHandler.java:163) [identityiq.jar:8.2 Build cfad9a66460-20210923-160543]
Kindly please help

Regards
Amit

11

Hi @ayadav_12,

this error means you a deadlock into DB. So 2 or more transation try to running on the same resource.

You can use this command DBCC TRACEON (1222, -1); for activating the logs for deadlock and keep more info.

For resolve this you can wait the end of current transaction or try to restart the service of DB.

Above all, a deadlock is an important warning that something is not correct about the maintenance or use of db. I suggest to you a complete review of db state and of all funcion that use it(external sailpoint too)

1 Like
12

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.