On 1/8/06, Zohar Amir <[EMAIL PROTECTED]> wrote: > Hello, > I've used tomcat to run some naive servlets, and now I need to do something > more complicated. I need to be able to distribute my service. Clients > connect to a tomcat server and their requests are forwarded to a backend > server. I need to be able to distribute all this, so that clients can > connect to any of a number of tomcat servers and then be "directed" to the > same backend server throughout their session (until they log out). > Can anyone point me to where I can read about such a solution? > What I thought was maintaining a database with a mapping of session -> > backend server, and use it, but this requires querying the database for each > transaction... > Any other ideas?] > Thanks, > Zohar.
You can store the info about the back-end server as an attribute in the session itself. Clustering and session replication will ensure that the servlets get the correct session info no matter which Tomcat server handles the request. (see http://192.168.1.12:8080/tomcat-docs/cluster-howto.html) You have a few choices for how the session info is replicated, some of which may be more efficient than using a database. -- Len --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
