> We're using apache 1.3.33 with tomcat 5.0.16, connected via mod_jk, on > Solaris.
This is very outdated. You shuld update to TC 5.0.30 and mod_jk 1.2.8. > What I'm observing is that "load-balancing" isn't working. We have a > couple of machines dedicated to our XML interface, and have apache > Now, in operation, machine-a is getting hammered, while machine-b gets > almost no traffic at all. Machine-a typically has CPU loads in the 4.0 > range, while machine-b sits idle at 0.04. > My hunch is that the bulk of the traffic is coming from a single > source, and so apache/mod_jk/something is deciding to give it over to > the same tomcat instance each time, even though it shouldn't be. Routing decisions are made by each Apache process independently. So directly after starting each apache process will forward it's first request to the same worker, it's second to the same other worker etc. After some time, because of differing answer times you will exhibit a balanced situation. Are you using Keep-Alive for HTTP? If your are having only few Clients and you are using very long Keep-Alive-Times maybe all clients will constantly use the same worker. But I#m not sure if it's true, although it would be an easy check to just disable Keep-Alive in Apache. Another possibility (after upgrading ;) ) is to use debug log level and study the output under low load. You didn't provide the full workers.properties file though. Are you having ONLY loadbalancer3 in the workers list? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
