Also, my point in mentioning an LB is that it should be done at the network
level so as to not incur the same overhead of a reverse proxy like Apache
(which is why this email started in the first place). At work we have zxtm
connecting to jboss/tomcat which does well enough. Obviously if you are
using the Resin<->Apache module, then that is another story entirely as
well. I assumed that the http layer in Resin is as good as Tomcat in terms
of stability. If that is not the case, then you should be using the R<->A
On Sat, Jan 16, 2010 at 10:02 AM, Scott Hernandez <
> It depends on what your services, performance, and bandwidth requirements
> Anyway, there are (a few) options.
> ldirectord - (low level) http://linux.die.net/man/8/ldirectord
> balance -- (low level) http://www.inlab.de/balance.html
> trafficmanager -- (yahoo lb turned open-source)
> zxtm -- (free/commercial)
> You can do this at the network level (MAC/IP) or application level (http,
> There are tons of reverse-proxies with load-balancing too.
> There is nothing wrong with using Apache and Resin, but people do use
> apache for things that aren't in its core set of features and then
> wonder why there are problems...
> On Sat, Jan 16, 2010 at 2:24 AM, Wesley Wu <wumen...@gmail.com> wrote:
> > Hi Jon & Scott,
> > I don't like apache either but resin 4.0.2 cluster web-tier seems
> > unstable for me.
> > I've not tested the 4.0.3 cluster.
> > My Apache config:
> > ResinHost 192.168.1.4 6801
> > ResinBackup 192.168.1.5 6801
> > Which load balancer will be more appropriate for this usage?
> > Thanks.
> resin-interest mailing list
resin-interest mailing list