Could that be because of lazy loading of some properties.
When the plugin tries to display some object lazily loaded, the
session is no longer valid and the object cannot be lazily
fetched. The result of .metadata/.log
net.sf.hibernate.HibernateException: Could not initialize
proxy - the owning Session was closed
at net.sf.hibernate.proxy.LazyInitializer.initialize
(LazyInitializer.java:44)
at
net.sf.hibernate.proxy.LazyInitializer.initializeWrapExceptions
(LazyInitializer.java:54)
.
.
.
.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Could that be because of lazy loading of some properties.
When the plugin tries to display some object lazily loaded, the
session is no longer valid and the object cannot be lazily
fetched. The result of .metadata/.log
net.sf.hibernate.HibernateException: Could not initialize
proxy - the owning Session was closed
at net.sf.hibernate.proxy.LazyInitializer.initialize
(LazyInitializer.java:44)
at
net.sf.hibernate.proxy.LazyInitializer.initializeWrapExceptions
(LazyInitializer.java:54)
.
.
.
.
Logged In: YES
user_id=181257
You might want to try what I suggested to 1076370 in a
comment.