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.
see: http://tomcat.apache.org/connectors-doc/generic_howto/workers.html and http://tomcat.apache.org/connectors-doc/reference/workers.htmlIf 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.htmlAs 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.
Oliver
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
