Using Ubuntu 64bit with mod_caucho behind Apache. The 4.0.23 config handled a simple 2 cluster + single server in each setup (servers "a" and "b"), which were started separately using resin.sh start -server a -conf/resin/conf/resin-a.xml and the same for server b. There are dedicated IP's for each, so the 4.0.23 config looked like this:
resin-a.xml <cluster id="cluster-a"> <server-default> <!-- The http port --> <http address="1.example.com" port="8080"/> resin-b.xml <cluster id="cluster-b"> <server-default> <!-- The http port --> <http address="2.example.com" port="8080"/> I see when each resin instance starts the line "http listening to x.example.com:8080" appears in the 4.0.23 start up log, correctly applicable to each IP. I set up the 4.0.27 config as closely as I could to this and get the conflict message on whichever starts the second - the first having hogged *:8080. I also see the line "http listening to *:8080" in each instances start up log, I'm sure this is the real cause but I just couldn't find where to control that IP in the new config. I did see the port change when I made local copies of the properties files and used them, ie. resin-x.properties with the http: entry, but nothing I did to either the web_servers or app_servers entries there affected the IP. Using the above 2 <http> entries in the new config files also made no difference. What am I missing please? _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
