Re: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-07 Thread Jason Joseph
Rainer Jung wrote: Be careful to secure access to WEB-INF and META-INF. Yup, Ive got this in there, one for META-INF too... deny from all Thanks... Regards, Rainer - To unsubscribe, e-mai

Re: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-06 Thread Jason Joseph
Rainer Jung wrote: The difference is obviously how the bunch of pictures is handled, that were retrieved close to the end. Those images - I suppose - are static content. They are very small. So needing 2 seconds to serve such an image is much to long. The previously send log files show, th

Re: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-05 Thread Jason Joseph
Rainer Jung wrote: JkOptions +FlushHeader +FlushPackets in order to make the flush also effective for httpd. Just realized I didn't disable caching before I did that last test, heres the image with caching disabled. http://207.7.102.90/~thecorp/apache-ajp-withflush-nocache.jpg Its

Re: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-05 Thread Jason Joseph
Rainer Jung wrote: On 05.06.2009 22:04, Christopher Schultz wrote: Chuck, On 6/5/2009 1:17 PM, Caldarale, Charles R wrote: From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: concurrent connections with mod_jk/apache/tomcat The only time when a browser would fire off "simultaneo

RE: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-04 Thread Caldarale, Charles R
> From: Jason Joseph [mailto:jjos...@keystreams.com] > Subject: Re: Re: concurrent connections with mod_jk/apache/tomcat > > after reading things online I thought the best practice for production > environments was for tomcat to handle dynamic requests and apache to > handle sta

Re: Re: concurrent connections with mod_jk/apache/tomcat

2009-06-04 Thread Jason Joseph
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jason, On 6/4/2009 5:06 PM, Jason Joseph wrote: I am currently in development of an app which we are testing through tomcat6 (websphere specifically). Now that we are moving to production we wanted to use apache (Apach