You might want to look at using the ProxyServlet on the front end (http://download.eclipse.org/jetty/stable-8/apidocs/index.html?org/eclipse/jetty/servlets/ProxyServlet.html). I found a few bugs with it a while back so I ended up writing my own but I believe that most of the issues have been resolved. We use it as a simple reverse/routing proxy in our test environments to route specific request paths to a bunch of backend servers. In production we use Cisco load balancers to do the same thing.
You may also want to check-out HAProxy (http://haproxy.1wt.eu/). I've used it before in other production environments and it was rock solid and very flexible. -mike [cid:[email protected]] | Mike Pilone | Software Architect, Distribution | [email protected]<mailto:[email protected]> | o: 202-513-2679 m: 703-969-7493 From: [email protected] [mailto:[email protected]] On Behalf Of Bill Harten Sent: Sunday, January 15, 2012 10:07 PM To: [email protected] Subject: [jetty-users] Request forwarding to services on different JVMs I need to forward requests for different virtual hosts (ABC.COM<http://abc.com/>, DEF.COM<http://def.com/>, etc.) to different JVMs (service for ABC.COM<http://abc.com/>, service for DEF.COM<http://def.com/>, etc.) on the same machine. Can Jetty (8) be used like Apache's mod_proxy this way? How? Any advantages or disadvantages? They need to be different JVMs for security and start/stop/crash isolation from each other. Requests need to all come to port 80 (or all to ssl port 443) because non-standard ports are often blocked for our users. Services could listen for 'forwards' on their own ports internally, if that would help. Ideas? Thanks.
<<inline: image001.jpg>>
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
