-
1. Re: using db instead of sticky sessions
brian.stansberry Jun 27, 2008 12:13 AM (in response to asookazian)Not sure if you are talking about web sessions or SFSBs or both. The referenced doc is about web sessions.
Anyway, for SFSBs at least, JBoss has no option to use a DB to persist your bean after every request. Passivation to the file system is supported, but that doesn't write the session to disk after every update; only when the bean should be swapped to disk to conserve memory.
So, if you want to cluster SFSBs you need to replicate them, and that requires sticky sessions.
Same basically applies to web sessions, although there is a web session manager in Tomcat (and perhaps in JBoss Web) that can write to a db. Not sure if that's only for passivation as well. Last I looked at it a couple of years ago it wasn't really production ready. Could have changed though. -
2. Re: using db instead of sticky sessions
asookazian Jun 30, 2008 6:50 PM (in response to asookazian)An SFSB’s state can be saved in a persistent store in case a server instance fails. The state of an SFSB is saved to the persistent store at predefined points in its life cycle. This is called checkpointing. If SFSB checkpointing is enabled, checkpointing generally occurs after any transaction involving the SFSB is completed, even if the transaction rolls back.
http://docs.sun.com/app/docs/doc/819-3672/beaib?a=view
So JBoss 4.2 or 5 AS does not have this capability? I'm wondering if any other JavaEE servers support checkpointing? This is most likely the route my team-member was interesting in going... -
3. Re: using db instead of sticky sessions
asookazian Jun 30, 2008 6:51 PM (in response to asookazian)"asookazian" wrote:
An SFSB's state can be saved in a persistent store in case a server instance fails. The state of an SFSB is saved to the persistent store at predefined points in its life cycle. This is called checkpointing. If SFSB checkpointing is enabled, checkpointing generally occurs after any transaction involving the SFSB is completed, even if the transaction rolls back.
http://docs.sun.com/app/docs/doc/819-3672/beaib?a=view
So JBoss 4.2 or 5 AS does not have this capability? I'm wondering if any other JavaEE servers support checkpointing? This is most likely the route my team-member was interesting in going...