We are using SailPoint IIQ 8.2p1 and we recently upgraded to 8.4. We are getting below error when the manager/system responsible raises a request. It is working fine when other users apart from manager/system responsible raises a request. Below is the error message.
“An unexpected error occurred: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session”
Hi @Joysiril,
that feels you are some problem to data on DB.
Try to active the HQL for keeping more info:
log4j.logger.org.hibernate=debug
log4j.logger.org.hibernate.cache=debug
o trace
Hi @enistri_devo,
Shall we add these loggers in log4j2.properties file.
Hi!
Could you check your code related to this functionality?
These errors are common if you are not retrieving objects properly in your rules. Look for big searches that keep iterating without fully reloading the object and try to “update” the object in memory with “context.getObjectByName” method before using the object.
Let us know if this works or share more details about the error!
Hi @Joysiril . Can you please share the XMLs by replacing the real time data with some values? I have came across this and depending on the errors:
a) For some, I used to delete the Role Bundles and then create a new one and try and after that the provisioning worked successfully.
b) For some, I used to delete the Entitlements and then add the Entitlements back again and after that the provisioning worked as expected.
By reading your post, it sounds like some filter or some configuration. Wanted to take a look into it and see what configurations or filters you used on the Role Bundle or any where else. Please let me know.
This issue usually occurs when you have loaded an object with one session and not all multi valued attributes where consumed yet. Then somewhere the session is closed. And at some late point in time you try to access those lazy multi valued attributes but the session no longer exists.
Easiest fix is to reload the object from the db with the current session. → new identity = context.getObjectById(oldIdentity.getId())
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.