Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008]

[James Carlson]

Petr Sumbera writes:
> >> + /usr/apache/libexec/mod_jk.so  uncommitted  Apache Tomcat connector
> > 
> > I'm a little confused by that.  Does this mean that the mod_jserv
> > mentioned in 2002/009 remains in place, and will continue to be used
> > for Tomcat 4.0?  (I'm unsure because that case seemed to say that
> > mod_jserv was too old for 4.0 as well ... but never mentioned the new
> > connector name.)
> 
> Apache 1.3 module mod_jserv.so remained on the place but as it's using 
> ajp12 it no longer works with Tomcat 4 (so it won't work with 5.5 either)

Does mod_jserv do anything useful if we don't have the Tomcat it goes
with?

> http://tomcat.apache.org/connectors-doc/generic_howto/workers.html

OK; so matching all of this up is "merely" a user configuration
problem, right?

> New module mentioned int that case was WebAPP (mod_webapp.so) which 
> communicated with Tomcat 4 via WARP protocol.

I didn't see that in the previous case:

% grep mod_ 2002/009/*
2002/009/20020104_ken.erickson: than the old mod_jserv connector that was used by
2002/009/mail:  than the old mod_jserv connector that was used by

In fact, a quick grep shows that this is the first mention of
mod_webapp in any PSARC case.  In any event, as long as customers are
somehow getting documentation that explains this confusing array of
connectors (that appear to have names that are unrelated to the
version supported), I'm puzzled, but happy enough.

(I'm guessing that mod_tom4 and mod_tom5 would have just been too
easy.  :-/)

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677