Sam,I suppose you mean :You can add http listeners like this: ... </cluster><http server-id="a" host="*" port="8080"/> <http server-id="b" host="*" port="8080"/> Then you will have both an srun listener (on port 6802) and an http listener (on port 8080) on each machine. <http server-id="a" host="192.168.11.181" port="6802"/> <http server-id="b" host="192.168.11.182" port="6802"/> <http server-id="c" host="*" port="8080"/> I am a bit confused here. In our production, apache will load balance to 2 machines, 192.168.11.181 (a) and 192.168.11.182 (b). Question 1: Why do you changed the host part from local ip to "*"? Will apache be able to find those 2 machines? Question 2: How can i reserved another srun with port 8080 so that i can go to http://192.168.11.181/proxooladmin or http://192.168.11.182/proxooladmin? A snippet of my apache httpd.conf: <VirtualHost some_external_ip:80> DocumentRoot /www/srs/registrar ServerName svr01 DirectoryIndex index.jsp ResinConfigServer 192.168.11.182 6802 ResinConfigServer 192.168.11.181 6802 CauchoStatus yes # do not remove, otherwise apache will serve the jsp source code once resin is down AddHandler caucho-request .jsp </VirtualHost> You are right. I guess i was confused. I should have used local ip instead. :DIf www.something.com resolves to your Apache machine, then using it will not go directly to the backend Resin server (because it resolves to the Apache machineThis is actually a better solution for my case (hope that you still will answer my q's above as i need that knowledge for other means). But i have tried that, sadly to no avail. I am using proxool0.9.0RC2, in case you need to know. Does that matter? Extra infos: Solaris 9 Apache 2059 Resin 3.0.19 proxool0.9.0RC2You can use a fake jsessionid to choose which backend server you want to go to. Resin uses the first character of the sessionid to identify the backend server to use, starting with `a' as the first backend server. If wwww.example.com is your Apache instance, then you can use: http://www.example.com/proxooladmin;jsessionid=abc for the first server and http://www.example.com/proxooladmin;jsessionid=bcd for the second server Sam wrote: We have successfully configure 2 resin servers (server a and server b in separate machines, does not have an internet ip) running with apache (exposed to the internet) load balancing module. Everything works fine. Here is a snippet of the cluster configuration in resin.conf: <cluster> <client-live-time>120s</client-live-time> <srun id="a" host="192.168.11.181" port="6802" index="1" > read-timeout="120s"/> <srun id="b" host="192.168.11.182" port="6802" index="2" > read-timeout="120s"/> </cluster> How can I configure the cluster to listen to 6802(for apache to use) and 8080(for me to use) at the same time when I run the startup command so that I can go to http://www.something.com:8080/proxooladmin?You can add http listeners like this: ... </cluster> <http server-id="a" host="*" port="8080"/> <http server-id="b" host="*" port="8080"/> Then you will have both an srun listener (on port 6802) and an http listener (on port 8080) on each machine. Also, do not set the client-live-time and read-timeout unless it is specifically in response to monitoring and troubleshooting done for your environment. Those are tricky values and the defaults should be fine in most circumstances.so that I can go to http://www.something.com:8080/proxooladmin?If www.something.com resolves to your Apache machine, then using it will not go directly to the backend Resin server (because it resolves to the Apache machine). You can use a fake jsessionid to choose which backend server you want to go to. Resin uses the first character of the sessionid to identify the backend server to use, starting with `a' as the first backend server. If wwww.example.com is your Apache instance, then you can use: http://www.example.com/proxooladmin;jsessionid=abc for the first server and http://www.example.com/proxooladmin;jsessionid=bcd for the second server -- Sam -- Warm regards, Jacky Wong |
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest