On 1/21/13 11:14 AM, Olaf Krische wrote:
> with resin2 a setup to loadbalance was pretty simple:
> LoadModule caucho_module modules/mod_caucho.so
> CauchoConfigFile /home/krische/resin/current/conf/resin.conf
> And "resin.conf" would contain N "srun" entries for N backend servers. Done.
> Even when resin.conf changes, mod_caucho would react accordingly. No restart
> of apache was necessary.
> My question: is that possible in resin4 without using any fancy resin pro
Since the resin.xml is now too flexible for a C-based parser to handle,
the backend Resin does the parsing and then forwards the configuration
on to mod_caucho.
So that's no longer possible.
> Because in the community edition i already fail to add N server into a
> <cluster/>-configuration. Because thats only available in Resin Pro.
> And to add N CauchoHosts manually in the httpd.conf and reload the whole
> apache is a pita. Also i need root-access for that.
> What would you guys recommend?
Well, we'd recommend buying a license, of course :)
> Or has anyone ever tried a different kind of loadbalancing than e.g.
> mod_proxy on apache?
mod_proxy should work fine too. I think we added a session option to
make sticky sessions easier for mod_proxy to handle.
> resin-interest mailing list
resin-interest mailing list