Getting could not initialize proxy - no Session

[canilkumar (Anilkumar C)]

Problem

Getting below error - An unexpected error occurred: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: sailpoint.object.Identity.capabilities, could not initialize proxy - no Session with below options on the identity refresh task

1. Refresh assigned, detected roles and promote additional entitlements
2. Provision assignments

[Siddu7183 (Byraboina Siddardha)]

Hello Anil,
https://developer.sailpoint.com/discuss/t/lazy-initialize-issue/55528

Check this, it is similar to the issue you mentioned

[iamksatish (Satish Kurasala)]

Looks like somewhere in your workflows or rule methods you are directly using objects instead of ids or names which can cause this issue.

[Saket95606 (Saket Kumar)]

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…

Resolution: Although I was unable to find the exact root cause, Tomcat restart resolved my issue.

[SivaLankapalli (Siva Sankar Lankapalli)]

Hi @canilkumar,

The main reason for this behavior is that the object’s state changes before you commit its state. To avoid this issue within a transaction or flow, do not modify the object’s state.

A simple solution is to refrain from passing the object to any method calls. Instead, always retrieve the object’s context and set the necessary data before saving.

Thanks
Siva Lankapalli