Comments for A Java geek

Comment on Managing web sessions by Nicolas Frankel

Nicolas Frankel — Wed, 10 Mar 2010 18:14:00 +0000

Martin, this is not entirely true: the setAttribute() has to be called only if using the DeltaManager. Otherwise, the session is wholly duplicated, no matter what (which has other disadvantages).

Regarding Terracotta, it’s true that it has to be clustered, but this is also true for Apache. It is out of the scope of this article, insofar as it is web session management, not redundant architecture.

Thanks for your input anyway.

Comment on Managing web sessions by martin grotzke

martin grotzke — Wed, 10 Mar 2010 10:45:35 +0000

Regarding tomcat’s session replication, IMO it’s worth to mention that session attributes are replicated if setAttribute was called, not if the if the object stored as session attribute was changed. So this is not really transparent to the application. And I wonder which web frameworks can be used with this requirement without additional action. However, I hope that i’m missing s.th. very simple so that this problem does not really exist. Anyone?

Regarding terracotta, I see the terracotta server as a single point of failure, so for a high-availability solution terracotta would have to be clustered, too.

Cheers,
Martin

P.s. to identify myself: i’m the creator of the memcached-session-manager, so i’m probably a little bit biased

Comment on Clustering Tomcat by A Java geek » Managing web sessions

A Java geek » Managing web sessions — Mon, 08 Mar 2010 20:21:46 +0000

[...] the previous article, I set up a cluster of 2 Tomcat instances in order to achieve load-balacing. It also offered [...]

Comment on Hibernate hard facts part 1 by Nicolas Frankel

Nicolas Frankel — Thu, 04 Mar 2010 18:10:52 +0000

Is the Session you’re refering to an HTTP session or an Hibernate Session? Could you be more specific in your question? What happens is a little vague.

Comment on Hibernate hard facts part 1 by btilford

btilford — Thu, 04 Mar 2010 02:16:48 +0000

What happens in the (probably most common) scenario where the object is retrieved during an http request and updated in another http request? e.g. When you update you are using a different Session.

Comment on Hibernate hard facts part 2 by Nicolas Frankel

Nicolas Frankel — Wed, 03 Mar 2010 18:21:19 +0000

Cascade doesn’t spare you the toil to associate your objects with each other. However, it let you save (or whatever) your master object without previously creating the dependent object.

Comment on Hibernate hard facts part 2 by Alex

Alex — Wed, 03 Mar 2010 16:41:41 +0000

To avoid those errors you can use cascade on your associations.

Comment on Hibernate hard facts part 3 by A Java geek » Hibernate hard facts – Part 5

A Java geek » Hibernate hard facts – Part 5 — Tue, 02 Mar 2010 20:20:36 +0000