-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anthony,
On 2/18/2009 4:43 PM, Anthony J. Biacco wrote: > 1. That's how I understood the documentation also. Maybe "Max" in > jkstatus refers to the max simultaneous connections it has done so > far, not the max it can do? I have no idea. Rainer or Mladen will have to answer this. Guys? > 2. Yeah, I tried the Executor attribute. Unfortunately, it doesn't > work on AJP connectors. But a good thought. Perhaps the DisableReuse > JkOption. I'll have to load test performance both ways. Really? It's documented to be supported here: http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html If it doesn't work, you should file a bug report. I'm not sure is DisableReuse is going to change anything... the Java threads are independent of that setting. The DisableReuse will just establish new ajp13 connections with the backend. The same set of threads will still handle the requests. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmcjFUACgkQ9CaO5/Lv0PAEWACeJY83r5pgaxevuChm5vTWU6vv bEAAn3ZKkf+3EcigpkcrMyHPF3Nmb5+9 =dA2C -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
