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.
-Wesley
It depends on what your services, performance, and bandwidth requirements are.
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)
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
I noticed when I registered my class as a HessianService it was no
longer able to inject it. Is this an expected behavior?
I am working against 4.0.3.
BTW. You can reproduce all the problems I'm find using our resin4.0.3
branch of subetha -
http://subetha.googlecode.com/svn/branches/resin4.0.3/.
Given that we have a nice and fairly complex open source reference
implementation application (subetha), it would be great if Scott (et. al)
would test Resin 4.x releases against it.
jon
On Sat, Jan 16, 2010 at 6:47 PM, Scott Hernandez scotthernan...@hotmail.com
wrote:
I noticed when I
