rep by Matthew Schmidt: We're seeing an interesting bug here. Resin in its default configuration seems to do a deep initialization of any object that is being serialized after login with Spring Security. In our case, this happens to be a User object that has some lazy loaded lists of objects, which contains other lazy loaded lists. When we use the regular Java serialization for sessions, this is fine. When we use the default configuration is goes through and executes what appears to be thousands of queries as it tries to initialize everything. Is this the intended behavior?

Additional Information

Attached Files

Relationships

Relationships

Notes

Notes

(0005067)
ferg 02-17-11 16:02

hessian/3b4i

This should already be fixed in Resin 4.0.14. Earlier versions of Hessian did use the default constructor, but current ones will use the same method as Java I/O serialization to create the object without calling the constructor.