On 10/03/2009, at 10:27 PM, Oliver Scheel wrote:
Out of curiosity, how does tomcat handle request routing across
multiple instances/servers. In a traditional deployment the
WOAdaptor apache module would take care of routing the request to
the appropriate application instance, how does this work under a
clustered tomcat deployment?
There is the traditional mod_jk which behaves a bit like the WO web
adaptor. You define workers (tomcat instances) and must take care of
that "sticky_sessions" work.
Yeah, the sticky session stuff sounds a lot like what WOAdaptor does.
If you want to have a "farm" (and I don't know if it is possible to
achieve with WO):
http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html
As far as I understand it requires session persistance across the
whole cluster. Perhaps it is possible to configure that without it,
otherwise WO will suck. It's useful for a J2EE based architecture
where your EJB can be anywhere.
WO needs more than just session persistence, it has stateful page
instances and a backtracking cache you need to return to, so you need
request routing within the cluster, or use something like torracotta
(assuming that would work).
--
Seeya...Q
Quinton Dolan - [email protected]
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
