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

[Petr Sumbera]

James Carlson wrote:

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

Ok, let's use "tomcat5".

Note (which is not directly related to this case):

"
I believe for Nevada we should try to make Tomcat independent on Apache 
1.3 (as we have now two versions in Solaris and Tomcat is often run in a 
standalone mode), plus use version in path: /usr/tomcat/[version]/ and 
/var/tomcat/[version]/.
"

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

Yes. But Tomcat configuration file name is server.xml.

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

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)

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

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

http://tomcat.apache.org/tomcat-4.1-doc/config/webapp.html

Petr