-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 J,
JNeuhoff wrote: > Hmm, this might be a good reason to upgrade to Apache 2.2.x then. Currently, > the mod_jk 1.2.20 in conjunction with Apache 2.0.59 is not suitable for a > production system running Windows 2003, and unfortunately we don't have > sysadmins for Linux or Unix, hence I am stuck with Windows 2003 as the > server OS. Not to be too much of a troll, but isn't the Windows part of this setup the part that makes it shaky for production? All of the Windows sysadmins that I have known personally always needed rolling-reboot policies on their servers just to keep them from crashing. Do you experience anything like that? > Has anybody been successfully running Apache 2.2.x with the mod_proxy_ajp on, > a production Windows 2003 server? If you are going to upgrade to Apache httpd 2.2, it might be worth re-trying your mod_jk tests to see if anything has changed. (Sorry if this suggestion doesn't make any sense at all... I hadn't been closely following your memory leak thread.) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFtQfj9CaO5/Lv0PARAuUzAKCFrnc7gEM2Ye4wWXlxarM1EXd6zQCeOPSf n25F9eoJ1DxHqzA4gX2q1Kc= =fhTO -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]