org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.Identity.exceptions, could not initialize proxy - no Session

[Praveencharan (Praveen Kumar)]

we are getting the below error while perform identity request maintenance task in identityiq.

org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.Identity.exceptions, could not initialize proxy - no Session

[mandarsane]

Hi @Praveencharan ,

Please check these threads below, might help

Lazy initialize issue

Which IIQ version are you inquiring about? Version 8.3 Share all details related to your problem, including any error messages you may have received. Hi Everyone, Has anyone faced failed to lazily initialize a collection of role : sailpoint.object.Rule.referenceRuls, could not initialize proxy - no Session issue ? We were facing this error message in Aggregation tasks as well as certification perform maintainace task. Although after tomcat restart we are no longer facing this issue but still…

Seeing increased Hibernate session failures after upgrade to 8.3

I’m seeing a lot of “failed to lazily initialize a collection of (whatever)” after the upgrade to 8.3. This happens, of course, if the object is detached from its Hibernate session. There is a consistent pattern of this within and after provisioning. In most cases, I can simply reload the Identity or Link objects in question after invoking the Provisioner. However, there are some cases that I don’t know how to handle neatly. Here is an example stack trace from our customer’s installation (with …

[naveenkumar3 (Naveen Kumar)]

can you please check if there are any corrupted IdentityRequest or Identity records (especially related to exceptions) that might be causing this job to fail?”

[robert-hails]

Similar issue posted a few days back that could help. I linked some support docs that are useful in troubleshooting this

Full Identity Refresh Task Fails with Below Errors

Hi @aniketnegi - these errors typically indicate a customization issue rather than a simple product configuration problem. The LazyInitializationException and the NonUniqueObjectException error are commonly seen when custom rules or workflows retain full SailPoint/Hibernate objects such as Identities/Links/Bundles/etc or when context.decache() is used incorrectly. I’d recommend reviewing your custom rules, workflows, or any custom logic initiated by your refresh task. Please look for: stori…

[neel193 (Neelmadhav Panda)]

@Praveencharan Is this error coming for specific request or when any specific user submitting request?or somethign else. Basically do you see any pattern?