On Thu, 28 Jun 2001, Justin Erenkrantz wrote:
> Tomcat's HTTP standalone connector isn't very good at parsing HTTP
> (but, I know the HTTP protocol too well to know where the pitfalls are).
> IMHO, Tomcat shouldn't be allowed to be a web server on its own. It
> needs a connector in front of it. So, just from a standards compliance
> standpoint, Tomcat's HTTP connector has major issues with it. ASF has a
> very fine Web server available, so Tomcat doesn't need to be a HTTP
> server.
sure, but it's _great_ for development not to have to worry about
connecting it to a web server.
> And, yes, mod_webapp is WAY too verbose. I hope that will be
> addressed soon (or I'll submit a patch to do so when I can get around
> to it). The other advantage of using mod_webapp (or mod_jk) is that
> you can now serve static pages from Apache which should blow away
> Tomcat w.r.t. speed. My bet is that Pier has just focused on
> functionality, not tuning the Warp code for performance.
yeah, well, the webapp which i'm working with (cocoon2) doesn't use much
of anything in the way of non-dynamic resources. :)
> > oh, also, i ran into an OutOfMemory error when i really slammed the
> > server. i hadn't experienced that before with tomcat standalone. could
> > there be a memory leak in the WarpConnector code? has anyone else run into
> > this?
>
> Hmm, I haven't seen anything, but I also haven't done massive load tests
> on it. I thought Java wasn't supposed to have memory leaks? -- justin
the java virtual machine implementation isn't supposed to, and for the
latest round from sun and blackdown, i largely believe that. however, it's
still possible to write java applications with memory leaks - if you keep
creating new Objects and don't ever lose their references, you'll run out
of memory sooner or later.
- donald
