RE: [Bench] mod_jk cache and socket timeout

EDD...oOOo..(_)..oOOo... > PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 > > > > >-Original Message- > >From: Jan Singer [mailto:[EMAIL PROTECTED]] > >Sent: Monday, June 24, 2002 7:41 PM > >To: [EMAIL PROTECTED] > >Subject: [Bench]

[Bench] mod_jk cache and socket timeout

Hi, here are some performance tests. I don't know why it's faster with the patch... Dual PIII 1 GHz, 512MB, Red Hat 7.1, ab running on another machine, 100 Mbit NICs d:-> Jan --- with options --- socket_timeout=900 --- cache_timeout=15 Server Software:Apache/1.3.22 Server Hostname:

RE: mod_jk cache and socket timeout

> > to be simple we could just use time() and getdifftime for > > 1.2.0 release. 1.2.1 could use more sophisticated code. > > > +1. > I'll rearange the cache_timeout to use the 0 as default meaning > disabled, OK? +1 at both, if my opinion matters ;-) d:-> Jan -- To unsubscribe, e-mail:

RE: Close to solution ( WAS RE: mod_jk testing)

'm new to this maybe someone should beat me ;-) d:-> Jan -Ursprüngliche Nachricht- Von: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 21. Juni 2002 12:49 An: Tomcat Developers List Cc: Mladen Turk; Glenn Nielsen; Jan Singer Betreff: RE: Close to solution ( WAS RE: mod

AJP13 connection through a firewall

Hi all, we use Apache and Tomcat on to machines (both on a SUN Solaris) with a firewall between them, which is configured to kill open and idle connections after 60 minutes. This is done in a way that mod_jk (from jakarta-tomcat-connectors-4.0.2-01) doesn't close the socket in the pool. So the fi