Hi everyone,

I'm not very happy to post this topic since everyone is so tired of the lazy collection initialization exception, and after reading the forum and the cos i found a solution, but my question about this is slightly different.

It all started with a org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed exception, resolved after reading all the stuff kindly posted. My problem, nevertheless, is that the misrunning appilcation has NOT been changed and this exception has started to be thrown after 3 months of fully-functionality. So, what problem can derive to this strange behaviour ? Is there any timeout for the session that was not - miraculousely - expired ? Or is there a max amount of memory released for hibernate that has been overflowed ?

I hope i can find any better solution or a root for my problem, thank you all !!!!

Are you telling us you have a session that stayed alive for 3Months?

This is like asking 'May you hold this lamp up, while I get a screw driver an then leave for vacation!'

If your session really stayed alive for so long (and was under some real use) it might be that you see some kind of integer roleover effect or something. But I would have expected some serious memory problems long before that.

Let your sessions die!

Hi schauder,

Tanhks for your interest.

No, the session has not been alive for three months, but the application overlaying the hibernate engine has been working for three months without any problem, but has started to throw this exception.