Hi Everybody,

I have a question about the architecture of tomcat and the sharing of
beans (typically accessed by JSP page code) with a scope of "session".

It seems to me that one major problem with JSP and session-scoped beans
on tomcat (and possibly other servlet engines ? i'm not trying to bag
tomcat specifically here !) is that I am restricted to a hardware
architecture of a *single webserver* running tomcat.

If I wish to run a 'load-balanced' (dns round robin most likely) server
configuration with multiple instances of tomcat sitting behind the same
URL, is there any known way in which to share session-scope java beans
created by one tomcat server across the other servers ?

The only way I can see to solve this problem is to push all session
information to a backend database accessible by all the webservers, and
to look up the session information from the database *each* time the
user moves from page to page (and potentially across tomcat servers).
This seems kludgy, and the database access requirements defeat both the
simplicity of the session-bean approach, and add overhead to the very
scalability and performance that you're trying to achieve by using
multiple servers.

Any guidance or relevent experiences much appreciated ...

Thanks in advance.


David Peterson



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to