After upgraded to content box 3.5 from 3.0 keep getting error message after any update made to the database. the error message is “failed to lazily initialize a collection of role: cbContent.contentVersions, could not initialize proxy - no Session” is this know error do i have to go back to ContentBox 3.0 which worked very well for me? FYI i am running ColdFusion 2016
I did restart the server and it did go away but after any database update like content, users first update would work but after that i am getting that error.
Wow, that does seem very weird, I don’t think we have encountered something like this before. Can you post your Application.cfc and update patch level of Adobe 2016 please
I did try updating to Last ColdFusion 2016 patch 4 also but still have the same issue. this happens after few insert/updates (1 - 3) to the database like updating contents or users
The reload on Change is going to eat up your server and memory. Be careful with this setting. Only use it for development and if you are doing on-the-fly java compilation in the lib folder.
Enable logSQL in the orm settings block and make sure you monitor the log files on WHY it fails. Basically it is saying the hibernate session does not exist when you are trying to log in to the system.
more information about this error and i was able to replicate.
i noticed that after my session expires this error occurs. like say i am logged in as admin and managing content and after my session expires i get login screen then if i try to login it throw that error message
failed to lazily initialize a collection of role: cbContent.contentVersions, could not initialize proxy - no Session.
Very long time later, and on a different version of ContentBox (4.2.1) ColdFusion 2018, but I’m having the exact experience on a new server we just stood up. Always happens after a session times out. The strange thing for us is we have this running on 3 other environments and this is the only one that fails. The difference between environments is that the server that is experiencing the issue is a Windows/IIS server while the 3 that aren’t are Linux/Nginx or Linux/undertow(via commandbox).
Where you able to reproduce and find a solution for this @lmajano?