Hello,

"Hibernate in Action" suggests storing detached persistent objects (graph) in Http session. But to my knowledge, this will cause performance/scalability issue in a load-balanced server cluster with replicated session. This is because that session replication in clusters (e.g. Tomcat 5 cluster) is expensive and perform badly for large session objects. However, if you want to be able to route client request to any server in the cluster, detached objects can only be replicated via session - (It cannot be stored in cookie :-)

I wonder how do other people solve this problem in really projects?

cheers
chuck

Sticky sessions -> no session replication =)

Thx for the reply.

But if the server serving the sticky session crashes, the cluster cannot failover new request to other servers. Any better idea?