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

[James Carlson]

Petr Sumbera writes:
> Tomcat is community software and we cannot be 100% sure. But it seems 
> that move from 4.0->4.1 was rather unusual (they changed even a name 
> (Jakarta/Apache):
> 
> http://www.mail-archive.com/users@tomcat.apache.org/msg37336.html

OK, that's what I was expecting here.

> > I ask because the "tomcat55" path name seems odd to me.  I would have
> > expected "tomcat5" here ... and dealing with a path that changes again
> > in the future would probably be annoying.
> 
> I have no problem with changing of the path. But from information we 
> have we cannot expect that there will be any other release for 5 version 
> beside 5.5.
> 
> http://tomcat.apache.org/whichversion.html
> http://wiki.apache.org/tomcat/TomcatVersions

Ah, I see.  Still, when it comes time to do "tomcat6," it'll look a
little confusing to have "tomcat55" in there, so I'd prefer just "5."

> Plan is to add condition to above rule that Tomcat 5.5 will be started 
> when it has configuration file and there is no one for version 4.0.

So, if I understand it right, it's something like this:

	if [ -f /var/apache/tomcat5/conf/tomcat.conf ]; then
		start tomcat5
	elif [ -f /var/apache/tomcat/conf/tomcat.conf ]; then
		start tomcat4
	fi

Is that right?  If so, then I get it now.  (Just checking that there
wasn't some other "switch" needed for the administrator.)

> Note, that tomcat.conf starts WebAPP Apache 1.3 module which won't 
> communicate with any other version of Tomcat than 4.0. Therefore if we 
> agree we can extend this case in following way:
> 
> 2.2 (at the end)
> 
> +In addition WebAPP Apache Tomcat connector which was introduced by
> +PSARC/2002/009 is also deprecated now and it runs with Tomcat 4.0 only.
> +Therefore new Apache Tomcat connector module mod_jk will be added so
> +that users using Apache together with Tomcat can migrate.

Just a nit: in ARC terms, "deprecated" is "Obsolete."  It means the
interface still exists, but new users shouldn't use it, and old ones
should migrate away.

> 3. Interface table
> 
> + /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.)

-- 
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