From jek3@train1.eng.sun.com Wed Jan 30 16:45:24 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0V0jNOx029890 for ; Wed, 30 Jan 2008 16:45:23 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0V0jFB4006349 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.Com>; Thu, 31 Jan 2008 00:45:22 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVH00501GRKIZ00@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 30 Jan 2008 17:45:20 -0700 (MST) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVH00IAHGRJ8Z70@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 30 Jan 2008 17:45:19 -0700 (MST) Received: from train1.eng.sun.com (train1.SFBay.Sun.COM [129.146.175.101]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0V0jIHp004445; Wed, 30 Jan 2008 16:45:18 -0800 (PST) Received: from train1.eng.sun.com (localhost [127.0.0.1]) by train1.eng.sun.com (8.13.3+Sun/8.13.3) with ESMTP id m0V0jAlc002613; Wed, 30 Jan 2008 16:45:10 -0800 (PST) Received: (from jek3@localhost) by train1.eng.sun.com (8.13.3+Sun/8.13.3/Submit) id m0V0jAYr002609; Wed, 30 Jan 2008 16:45:10 -0800 (PST) Date: Wed, 30 Jan 2008 16:45:10 -0800 (PST) From: Joseph Kowalski Subject: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] To: PSARC-ext@sun.com, Petr.Sumbera@sun.com Message-id: <200801310045.m0V0jAYr002609@train1.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 3912 I'm sponsoring this fast-track for Petr Sumbera. It times out 02/06/08. I don't expect this is an easy case. It could actually be derailed. The issue is that Tomcat is currently not contained in a versioned path, yet Tomcat 5.5 is incompatable with what exists. Other that little detail, this is pretty obvious. Should be fun. - jek3 Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Tomcat 5.5 1.2. Name of Document Author/Supplier: Author: Petr Sumbera 1.3 Date of This Document: 30 January, 2008 4. Technical Description 0. Previous ARC cases PSARC/2002/009 - Jakarta Tomcat 4.0.1 PSARC 2001/266 - Jakarta Tomcat for Apache PSARC 1999/542 - Apache for Solaris 1. Introduction Solaris 10 and 9 contain deprecated Jakarta Tomcat 4.0.5. As this version contains many security vulnerabilities and simple update via patch to supported Apache Tomcat is not possible without major migration efforts, this document proposes to ship beside existing Tomcat also Apache Tomcat 5.5. 2. Details 2.1 Background According to security audit Jakarta Tomcat 4.0.5 bundled with Solaris 10 and 9 is vulnerable to thirteen known security issues (see list at section 4). This version of Tomcat is considered as deprecated and not supported by community for a long time. Update to Apache Tomcat 4.1 which is still being sporadically supported for security problems or to community fully supported version 5.5 (which is now in Nevada) would require users to recompile their application and possibly deal with several other incompatibilities with custom Realms, Valves or deprecated Apache Tomcat connector. Therefore the update isn't possible. There is also no possibility to fix all these vulnerabilities by ourself as not all information is available. 2.2. Solution The safest solution for customers is to provide them possibility to deal with these security threats at their own speed by adding yet another Tomcat into different path which would be delivered as part of original packages via patch. Tomcat as defined by PSARC/2002/009 uses /usr/apache/tomcat and /var/apache/tomcat directory for Tomcat files. This PSARC adds also /usr/apache/tomcat55 and /var/apache/tomcat55 for files which belongs to community supported version of Apache Tomcat 5.5.25. The release binding is Patch. 3. Interface table Lists only newly defined paths from PSARC/2002/0096 NAME STABILITY NOTES /usr/apache/tomcat55/bin uncommitted startup scripts /usr/apache/tomcat55/classes uncommitted Tomcat components /usr/apache/tomcat55/common uncommitted Tomcat components /usr/apache/tomcat55/lib uncommitted Tomcat jar files /usr/apache/tomcat55/server uncommitted Tomcat components /var/apache/tomcat55/conf uncommitted Tomcat configuration files /var/apache/tomcat55/logs uncommitted runtime log files /var/apache/tomcat55/webapps uncommitted Example applications /var/apache/tomcat55/temp uncommitted temporary files /var/apache/tomcat55/work uncommitted servlet engine work directory 4. List of vulnerabilities in Solaris 10 and 9 Tomcat 4.0.5 CVE-2002-1148, CVE-2002-1394, CVE-2002-2006, CVE-2003-0866, CVE-2005-2090, CVE-2005-3164, CVE-2005-3510, CVE-2006-3835, CVE-2007-0450, CVE-2007-1355, CVE-2007-1358, CVE-2007-2450, CVE-2007-5461 5. References Tomcat Documentation http://tomcat.apache.org/ Apache Documentation http://httpd.apache.org/docs/ PSARC/2002/009 - Jakarta Tomcat 4.0.1 PSARC 2001/266 - Jakarta Tomcat for Apache PSARC 1999/542 - Apache for Solaris 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From carlsonj@phorcys.east.sun.com Thu Jan 31 05:45:28 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VDjSB3017178 for ; Thu, 31 Jan 2008 05:45:28 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0VDjOWP007522; Thu, 31 Jan 2008 06:45:24 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVI0010ZGVMA800@brm-avmta-1.central.sun.com>; Thu, 31 Jan 2008 06:45:22 -0700 (MST) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVI00MW2GVLVW40@brm-avmta-1.central.sun.com>; Thu, 31 Jan 2008 06:45:22 -0700 (MST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m0VDjLb2018091; Thu, 31 Jan 2008 08:45:21 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m0VDjLEX018088; Thu, 31 Jan 2008 08:45:21 -0500 (EST) Date: Thu, 31 Jan 2008 08:45:21 -0500 From: James Carlson Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <200801310045.m0V0jAYr002609@train1.eng.sun.com> To: Joseph Kowalski Cc: PSARC-ext@sun.com, Petr.Sumbera@sun.com Message-id: <18337.53489.519274.517174@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> Status: RO Content-Length: 1231 Joseph Kowalski writes: > Update to Apache Tomcat 4.1 which is still being sporadically supported > for security problems or to community fully supported version 5.5 (which > is now in Nevada) would require users to recompile their application and > possibly deal with several other incompatibilities with custom Realms, > Valves or deprecated Apache Tomcat connector. Therefore the update isn't > possible. I see that 4.0->4.1 amounts to effectively a major version change, as it doesn't provide application compatibility. Is this also the upstream source plan for the future? In other words, should we expect that 5.6 will be incompatible with 5.5 in a similar way, or is the 4.0->4.1 event an unexpected problem? 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. > Lists only newly defined paths from PSARC/2002/0096 How do users select which one they want to run? -- James Carlson, Solaris Networking 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 From Petr.Sumbera@sun.com Thu Jan 31 07:57:25 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VFvP2v021377 for ; Thu, 31 Jan 2008 07:57:25 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0VFvOd0014352 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 31 Jan 2008 07:57:24 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVI0080FMZNUU00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 07:57:23 -0800 (PST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVI003STMZLUT50@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 07:57:22 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0VFvKdh000674 for ; Thu, 31 Jan 2008 15:57:20 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVI00J01MSYBI00@fe-emea-09.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 15:57:20 +0000 (GMT) Received: from [129.157.71.67] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVI008DJMZENOD0@fe-emea-09.sun.com>; Thu, 31 Jan 2008 15:57:15 +0000 (GMT) Date: Thu, 31 Jan 2008 16:57:14 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <18337.53489.519274.517174@gargle.gargle.HOWL> Sender: Petr.Sumbera@sun.com To: James Carlson Cc: Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A1EFDA.8020208@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.0 (X11/20070522) Status: RO Content-Length: 2516 James Carlson wrote: > Joseph Kowalski writes: >> Update to Apache Tomcat 4.1 which is still being sporadically supported >> for security problems or to community fully supported version 5.5 (which >> is now in Nevada) would require users to recompile their application and >> possibly deal with several other incompatibilities with custom Realms, >> Valves or deprecated Apache Tomcat connector. Therefore the update isn't >> possible. > > I see that 4.0->4.1 amounts to effectively a major version change, as > it doesn't provide application compatibility. > > Is this also the upstream source plan for the future? In other words, > should we expect that 5.6 will be incompatible with 5.5 in a similar > way, or is the 4.0->4.1 event an unexpected problem? 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 > 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 >> Lists only newly defined paths from PSARC/2002/0096 > > How do users select which one they want to run? Tomcat is started (beside manually) via Apache 1.3 init script (/etc/init.d/apache) when Apache configuration file (httpd.conf) includes tomcat.conf and Tomcat configuration file exists (server.xml). 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. 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. 3. Interface table + /usr/apache/libexec/mod_jk.so uncommitted Apache Tomcat connector 5. References + http://tomcat.apache.org/connectors-doc/ -- Petr From carlsonj@phorcys.east.sun.com Thu Jan 31 08:56:01 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VGu1xJ023582 for ; Thu, 31 Jan 2008 08:56:01 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0VGtvTg003641; Thu, 31 Jan 2008 08:55:59 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVI00F0DPPBLH00@brm-avmta-1.central.sun.com>; Thu, 31 Jan 2008 09:55:59 -0700 (MST) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVI005PLPPA6HE0@brm-avmta-1.central.sun.com>; Thu, 31 Jan 2008 09:55:58 -0700 (MST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m0VGtwOv018779; Thu, 31 Jan 2008 11:55:58 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m0VGtwP2018776; Thu, 31 Jan 2008 11:55:58 -0500 (EST) Date: Thu, 31 Jan 2008 11:55:58 -0500 From: James Carlson Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A1EFDA.8020208@sun.com> To: Petr Sumbera Cc: Joseph Kowalski , PSARC-ext@sun.com Message-id: <18337.64926.71792.335314@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> Status: RO Content-Length: 2634 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 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 From John.Plocher@sun.com Thu Jan 31 09:26:55 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VHQtNW024925 for ; Thu, 31 Jan 2008 09:26:55 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0VHQsWB015641 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 31 Jan 2008 10:26:55 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVI0051BR4VT900@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 09:26:55 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVI00KFJR4TS5C0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 09:26:53 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0VHQr3c006152 for ; Thu, 31 Jan 2008 09:26:53 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVI00F01QUE8W00@fe-sfbay-10.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 09:26:53 -0800 (PST) Received: from wp668.SFBay.Sun.COM ([129.146.226.219]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVI001I4R4R7080@fe-sfbay-10.sun.com>; Thu, 31 Jan 2008 09:26:51 -0800 (PST) Date: Thu, 31 Jan 2008 09:26:51 -0800 From: John Plocher Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A1EFDA.8020208@sun.com> Sender: John.Plocher@sun.com To: Petr Sumbera Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A204DB.7020409@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 160 Petr Sumbera wrote: > Tomcat is started (beside manually) via Apache 1.3 init script What about Apache 2.x - how does this work with that version? -John From jek3@sun.com Thu Jan 31 12:35:40 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VKZeRv002881 for ; Thu, 31 Jan 2008 12:35:40 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0VKZUgs007682; Thu, 31 Jan 2008 20:35:37 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVI00D0JZVD2M00@nwk-avmta-2.sfbay.sun.com>; Thu, 31 Jan 2008 12:35:37 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVI00CX6ZVCKG10@nwk-avmta-2.sfbay.sun.com>; Thu, 31 Jan 2008 12:35:36 -0800 (PST) Received: from [129.150.12.37] (vpn-129-150-12-37.SFBay.Sun.COM [129.150.12.37]) by jurassic-x4600.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m0VKZZCD571892; Thu, 31 Jan 2008 12:35:36 -0800 (PST) Date: Thu, 31 Jan 2008 10:34:10 -1000 From: Joseph Kowalski Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A1EFDA.8020208@sun.com> To: Petr Sumbera Cc: James Carlson , Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A230C2.40008@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Status: RO Content-Length: 873 Petr Sumbera wrote: >> 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 What I think Jim is getting at, that versioning at the level of a Major release (of Tomcat) is seems rather obvious. (Why we didn't make tomcat be tomcat4? Darn!) We need to *try* to look into our crystal balls to believe if Tomcat will follow a paradigm of "no incomatibilities in Tomcat Minor releases). Also, if the community was to create a compatible 5.6 version, what would we do? - jek3 From peter.tribble@gmail.com Thu Jan 31 13:18:33 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0VLIXTB004468 for ; Thu, 31 Jan 2008 13:18:33 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m0VLIVZ4021747 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 31 Jan 2008 13:18:33 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVJ00C0H1UWVV00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 14:18:32 -0700 (MST) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVJ00FC21UPO0E0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 31 Jan 2008 14:18:30 -0700 (MST) Received: from relay22.sun.com (relay22.sun.com [192.12.251.34] (may be forged)) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0VL3faT004454 for ; Thu, 31 Jan 2008 21:18:25 +0000 (GMT) Received: from mms22es.sun.com ([150.143.232.34] [150.143.232.34]) by relay22i.sun.com with ESMTP id BT-MMP-2614262 for PSARC-ext@sun.com; Thu, 31 Jan 2008 21:18:25 +0000 (Z) Received: from relay23.sun.com (relay23.sun.com [192.12.251.54]) by mms22es.sun.com with ESMTP id BT-MMP-886222 for PSARC-ext@sun.com; Thu, 31 Jan 2008 21:18:24 +0000 (Z) Received: from wr-out-0506.google.com ([64.233.184.229] [64.233.184.229]) by relay23i.sun.com with ESMTP id BT-MMP-16563890 for PSARC-ext@sun.com; Thu, 31 Jan 2008 21:18:24 +0000 (Z) Received: by wr-out-0506.google.com with SMTP id c53so863646wra.22 for ; Thu, 31 Jan 2008 13:18:24 -0800 (PST) Received: by 10.142.225.11 with SMTP id x11mr1600925wfg.141.1201814303070; Thu, 31 Jan 2008 13:18:23 -0800 (PST) Received: by 10.142.207.7 with HTTP; Thu, 31 Jan 2008 13:18:23 -0800 (PST) Date: Thu, 31 Jan 2008 21:18:23 +0000 From: Peter Tribble Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A230C2.40008@sun.com> To: Joseph Kowalski Cc: Petr Sumbera , PSARC-ext@sun.com, Joseph Kowalski , James Carlson Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=roscp5q1o9VpO3pvgfpb/WM+h3XE19EbJ5T9SDnDNXU=; b=nakJU0pl7uzT1kMvmFFS9aLxZd0GNkunoZifJM+oftqCEY3f/zA2tf/6oej71cziC7t8vOkOSae2IspOB+vEJLk1q7sh3FO9+2WLqZOVSNVXhUbCKCpXZLq/TH7o6R20NPT/Vto4LK5N9iowVOyGMcHAxK0wVPaVTgN2vZOpt1c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hRfzcDINglhHpZeVRKiBDmPbxhH4750LCSfVS8JtvSHh5YyXtpDizWGW2YPTIZm+7CYfDcQsyKA4/xDlXR9A0j9sMSK8DPr/5tPDA7zP/nYYU97DXm6MOpo90aT767W7U2X2VR8Ew30Ltie6qT4GZHEP+t560vlMehY7cuIPXRM= X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 0.082sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A230C2.40008@sun.com> Status: RO Content-Length: 1849 On Jan 31, 2008 8:34 PM, Joseph Kowalski wrote: > Petr Sumbera wrote: > >> 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 > What I think Jim is getting at, that versioning at the level of a Major > release (of Tomcat) is > seems rather obvious. (Why we didn't make tomcat be tomcat4? Darn!) > > We need to *try* to look into our crystal balls to believe if Tomcat > will follow a paradigm > of "no incomatibilities in Tomcat Minor releases). > > Also, if the community was to create a compatible 5.6 version, what > would we do? As a user who has deployed essentially every version of tomcat that has come out, the version numbering scheme doesn't quite follow a major.minor approach. As I understand it, the major version reflects the servlet/jsp spec version; the minor versions are significantly different implementation tracks. And historically you really do care about the fact that 4.0 and 4.1 were different, and that 5.0 and 5.5 were different. Certainly when we talk about tomcat versions in the day job, it's '5.5' not '5'. (We wouldn't ever want to accidentally get tripped up by 5.0.) So to me 'tomcat55' looks quite natural :-) But I would be happy with tomcat5 at this stage, now that there's no likelihood of it being confused with 5.0, and I wouldn't expect another 5.x now that 6 is the main focus of development. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ From Petr.Sumbera@sun.com Fri Feb 1 05:20:18 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11DKHvg000473 for ; Fri, 1 Feb 2008 05:20:18 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m11DJuZq001764 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 13:20:16 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00L1FADN8O00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 05:20:11 -0800 (PST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00B7YADLQ290@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 05:20:10 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11DK9IV007074 for ; Fri, 01 Feb 2008 13:20:09 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK009019ZZT600@fe-emea-10.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 13:20:09 +0000 (GMT) Received: from [10.162.39.206] ([85.160.7.151]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK0015MADFFGD0@fe-emea-10.sun.com>; Fri, 01 Feb 2008 13:20:05 +0000 (GMT) Date: Fri, 01 Feb 2008 14:20:03 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <18337.64926.71792.335314@gargle.gargle.HOWL> Sender: Petr.Sumbera@sun.com To: James Carlson Cc: Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A31C83.1020702@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 2518 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 From casper@holland.sun.com Fri Feb 1 05:42:05 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11Dg4nu000598 for ; Fri, 1 Feb 2008 05:42:05 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m11DfjaQ009538 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.COM>; Fri, 1 Feb 2008 13:42:04 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00G05BE1ZK00@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 01 Feb 2008 06:42:01 -0700 (MST) Received: from dm-holland-02.uk.sun.com ([129.156.101.225]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK007R0BE05A50@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 01 Feb 2008 06:42:01 -0700 (MST) Received: from holland (room101.Holland.Sun.COM [10.16.117.40]) by dm-holland-02.uk.sun.com (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id m11DfxXN021131; Fri, 01 Feb 2008 13:41:59 +0000 (GMT) Date: Fri, 01 Feb 2008 14:41:59 +0100 From: Casper.Dik@sun.com Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A31C83.1020702@sun.com> Sender: casper@holland.sun.com To: Petr Sumbera Cc: James Carlson , Joseph Kowalski , PSARC-ext@sun.com Message-id: <200802011341.m11DfxXN021131@dm-holland-02.uk.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> Status: RO Content-Length: 972 >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]/. >" And it would be nice if Sun Ray Server Software would work with tomcat as shipped without having to add a bunch of links as is the case now; SRSS does ship with a tomcat bundle, but I prefer not to have multiple copies of the same software installed). The question raised when I asked the SRSS folks about this was "yes that would be nice but how about support?" What level of support can one expect for Tomcat (managed, I think, is the current value) Casper From Petr.Sumbera@sun.com Fri Feb 1 05:45:13 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11DjC0Z000616 for ; Fri, 1 Feb 2008 05:45:13 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m11DjBEf001866 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 21:45:11 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00M01BJADT00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 05:45:10 -0800 (PST) Received: from gmp-eb-mail-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00BZFBJ9PYA0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 05:45:10 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11Dj9ZR016084 for ; Fri, 01 Feb 2008 13:45:09 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00201B6M8G00@fe-emea-09.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 13:45:09 +0000 (GMT) Received: from [10.162.39.206] ([85.160.7.151]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK00JJTBJ66Z50@fe-emea-09.sun.com>; Fri, 01 Feb 2008 13:45:08 +0000 (GMT) Date: Fri, 01 Feb 2008 14:45:06 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A204DB.7020409@Sun.Com> Sender: Petr.Sumbera@sun.com To: John Plocher Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A32262.8020800@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A204DB.7020409@Sun.Com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 704 John Plocher wrote: > Petr Sumbera wrote: >> Tomcat is started (beside manually) via Apache 1.3 init script > > What about Apache 2.x - how does this work with that version? Answer is simple. It doesn't work. Tomcat was introduced when there was no Apache 2. Tomcat is located in Apache 1.3 subdirectory (usr/apache) and not in Apache 2 subdirectory (usr/apache2). But still it can be manually configured and run as stand-alone server or to communicate with Apache 2. The best way is probably to reuse /etc/init.d/apache. For Apache 2.2 (in Nevada) there is by default mod_proxy_ajp.so which communicates via AJP13 protocol. While for Apache 2.0 (Solaris 10) mod_jk has to be compiled. Petr From carlsonj@phorcys.east.sun.com Fri Feb 1 05:57:44 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11Dvh7C001158 for ; Fri, 1 Feb 2008 05:57:44 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m11DvReV005214; Fri, 1 Feb 2008 21:57:40 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00G0LC40HT00@nwk-avmta-1.sfbay.Sun.COM>; Fri, 01 Feb 2008 05:57:36 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00H8OC3ZTLB0@nwk-avmta-1.sfbay.Sun.COM>; Fri, 01 Feb 2008 05:57:35 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m11DvZbP010627; Fri, 01 Feb 2008 08:57:35 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m11DvZKt010624; Fri, 01 Feb 2008 08:57:35 -0500 (EST) Date: Fri, 01 Feb 2008 08:57:35 -0500 From: James Carlson Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A31C83.1020702@sun.com> To: Petr Sumbera Cc: Joseph Kowalski , PSARC-ext@sun.com Message-id: <18339.9551.167704.157019@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> Status: RO Content-Length: 1742 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 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 From Petr.Sumbera@sun.com Fri Feb 1 06:09:52 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11E9pSk001527 for ; Fri, 1 Feb 2008 06:09:51 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m11E9a12009855 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 1 Feb 2008 22:09:50 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK0000DCOA4N00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 01 Feb 2008 06:09:46 -0800 (PST) Received: from gmp-eb-mail-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00B3MCO8Q5D0@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 01 Feb 2008 06:09:44 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11E9hIc019453 for ; Fri, 01 Feb 2008 14:09:43 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00201B6M8G00@fe-emea-09.sun.com> (original mail from Petr.Sumbera@Sun.COM) for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Fri, 01 Feb 2008 14:09:43 +0000 (GMT) Received: from [10.162.39.206] ([85.160.7.151]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK00J0CCO56ZH0@fe-emea-09.sun.com>; Fri, 01 Feb 2008 14:09:43 +0000 (GMT) Date: Fri, 01 Feb 2008 15:09:42 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: Sender: Petr.Sumbera@sun.com To: Peter Tribble Cc: Joseph Kowalski , PSARC-ext@sun.com, Joseph Kowalski , James Carlson Message-id: <47A32826.3020809@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A230C2.40008@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 1270 Peter Tribble wrote: >> We need to *try* to look into our crystal balls to believe if Tomcat >> will follow a paradigm >> of "no incomatibilities in Tomcat Minor releases). >> >> Also, if the community was to create a compatible 5.6 version, what >> would we do? > > As a user who has deployed essentially every version of tomcat > that has come out, the version numbering scheme doesn't > quite follow a major.minor approach. As I understand it, the > major version reflects the servlet/jsp spec version; the minor > versions are significantly different implementation tracks. > And historically you really do care about the fact that > 4.0 and 4.1 were different, and that 5.0 and 5.5 were > different. > > Certainly when we talk about tomcat versions in the day job, > it's '5.5' not '5'. (We wouldn't ever want to accidentally get > tripped up by 5.0.) So to me 'tomcat55' looks quite natural :-) Exactly as Peter wrote. We cannot expect anything else beside 5.5 in version 5. And we can be quite confident with community support for this branch as they are still supporting 4.1 and 3.3. From this point of view choosing version 4.0 was rather unfortunate. For the same reason I would be afraid of choosing now version 6.0 (as it's being developed). Petr From Petr.Sumbera@sun.com Fri Feb 1 06:16:38 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11EGbbT002326 for ; Fri, 1 Feb 2008 06:16:38 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m11EGYgU012286 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 22:16:36 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00005CZNDI00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 06:16:35 -0800 (PST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00B1ECZLQ4C0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 06:16:35 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11EGWvs016411 for ; Fri, 01 Feb 2008 14:16:32 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00701CNQUH00@fe-emea-10.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 14:16:32 +0000 (GMT) Received: from [10.162.39.206] ([85.160.7.151]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK00LZKCZGZF50@fe-emea-10.sun.com>; Fri, 01 Feb 2008 14:16:30 +0000 (GMT) Date: Fri, 01 Feb 2008 15:16:28 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <200802011341.m11DfxXN021131@dm-holland-02.uk.sun.com> Sender: Petr.Sumbera@sun.com To: Casper.Dik@sun.com Cc: James Carlson , Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A329BC.9070906@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> <200802011341.m11DfxXN021131@dm-holland-02.uk.sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 261 Casper.Dik@Sun.COM wrote: > What level of support can one expect for Tomcat (managed, I think, is the > current value) Yes, Tomcat support is managed (as majority of all open source programs in Solaris). http://www.sun.com/software/solaris/freeware/ Petr From carlsonj@phorcys.east.sun.com Fri Feb 1 07:02:34 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11F2Y37002966 for ; Fri, 1 Feb 2008 07:02:34 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m11F2Svm017142; Fri, 1 Feb 2008 07:02:32 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00M4HF45BS00@nwk-avmta-1.sfbay.Sun.COM>; Fri, 01 Feb 2008 07:02:29 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK00H5CF44U9D0@nwk-avmta-1.sfbay.Sun.COM>; Fri, 01 Feb 2008 07:02:29 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m11ElTI4010892; Fri, 01 Feb 2008 09:47:29 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m11ElTR3010889; Fri, 01 Feb 2008 09:47:29 -0500 (EST) Date: Fri, 01 Feb 2008 09:47:28 -0500 From: James Carlson Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A32826.3020809@sun.com> To: Petr Sumbera Cc: Peter Tribble , Joseph Kowalski , PSARC-ext@sun.com, Joseph Kowalski Message-id: <18339.12544.951977.898959@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A230C2.40008@sun.com> <47A32826.3020809@sun.com> Status: RO Content-Length: 982 Petr Sumbera writes: > > Certainly when we talk about tomcat versions in the day job, > > it's '5.5' not '5'. (We wouldn't ever want to accidentally get > > tripped up by 5.0.) So to me 'tomcat55' looks quite natural :-) > > Exactly as Peter wrote. We cannot expect anything else beside 5.5 in > version 5. And we can be quite confident with community support for this > branch as they are still supporting 4.1 and 3.3. Thanks for the explanation. It sounds like "5.6," even if it did show up, wouldn't necessarily be a progression of any sort from "5.5." In that case, I'm happy with the "tomcat55" or even with "tomcat5.5". Your choice; the name itself isn't really architectural -- the only issue is capturing the right subset of information there. -- James Carlson, Solaris Networking 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 From Petr.Sumbera@sun.com Fri Feb 1 08:19:17 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11GJGYl003855 for ; Fri, 1 Feb 2008 08:19:16 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m11GJ8ci017976 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 16:19:15 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK0051AINZRB00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 09:19:11 -0700 (MST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK007DBINS59F0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 09:19:07 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11GJ4hd004362 for ; Fri, 01 Feb 2008 16:19:04 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00I01IGLZM00@fe-emea-10.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 16:19:04 +0000 (GMT) Received: from [10.162.39.206] ([85.160.7.151]) by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK009EOINN7UC0@fe-emea-10.sun.com>; Fri, 01 Feb 2008 16:19:01 +0000 (GMT) Date: Fri, 01 Feb 2008 17:18:58 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <18339.9551.167704.157019@gargle.gargle.HOWL> Sender: Petr.Sumbera@sun.com To: James Carlson Cc: Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A34672.6090909@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> <18339.9551.167704.157019@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 2008 James Carlson wrote: > 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? Well, mod_jserv was proposed to Solaris before Tomcat itself (LSARC/2000/024). So it is somehow related to Solaris WBEM Services. It might be also possible it's being used by SUNWasu - Sun Java System Application Server. >> http://tomcat.apache.org/connectors-doc/generic_howto/workers.html > > OK; so matching all of this up is "merely" a user configuration > problem, right? Yes. >> 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. There is plan to issue Sun Alert suggesting to migrate to Tomcat 5.5. We can make note there. There is also some space in patch README file for notes. > (I'm guessing that mod_tom4 and mod_tom5 would have just been too > easy. :-/) We don't live in a perfect world :-) Petr From John.Plocher@sun.com Fri Feb 1 09:43:59 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11HhwVD006520 for ; Fri, 1 Feb 2008 09:43:58 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m11HhumF004594 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 17:43:57 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00C03ML82T00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 10:43:56 -0700 (MST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK0053QML7RI40@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 10:43:56 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11Hhtf3003294 for ; Fri, 01 Feb 2008 09:43:55 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00A01MDE9U00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 09:43:55 -0800 (PST) Received: from [192.168.168.4] ([208.74.177.212]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK003DUML76JD0@fe-sfbay-09.sun.com>; Fri, 01 Feb 2008 09:43:55 -0800 (PST) Date: Fri, 01 Feb 2008 09:43:55 -0800 From: John Plocher Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A32262.8020800@sun.com> Sender: John.Plocher@sun.com To: Petr Sumbera Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A35A5B.7050605@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A204DB.7020409@Sun.Com> <47A32262.8020800@sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 897 Petr Sumbera wrote: > John Plocher wrote: >> Petr Sumbera wrote: >>> Tomcat is started (beside manually) via Apache 1.3 init script >> >> What about Apache 2.x - how does this work with that version? > > Answer is simple. It doesn't work. OK, but... > > Tomcat was introduced when there was no Apache 2. Tomcat is located in > Apache 1.3 subdirectory (usr/apache) and not in Apache 2 subdirectory > (usr/apache2). > > But still it can be manually configured and run as stand-alone server or > to communicate with Apache 2. The best way is probably to reuse > /etc/init.d/apache. > > For Apache 2.2 (in Nevada) there is by default mod_proxy_ajp.so which > communicates via AJP13 protocol. While for Apache 2.0 (Solaris 10) > mod_jk has to be compiled. ... here you say that it *does* work. I'm confused. What do I need to do if I run Apache2 and wish to use tomcat5.5? -John From John.Plocher@sun.com Fri Feb 1 10:18:33 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11IIWce007511 for ; Fri, 1 Feb 2008 10:18:33 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m11IIUWq021788 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 1 Feb 2008 18:18:31 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00G03O6UFZ00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 10:18:30 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK0000KO6UQSF0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 10:18:30 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m11IIUY4006352 for ; Fri, 01 Feb 2008 10:18:30 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVK00101NVK5E00@fe-sfbay-10.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 01 Feb 2008 10:18:30 -0800 (PST) Received: from [192.168.168.4] ([208.74.177.212]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVK00FO8O6TU660@fe-sfbay-10.sun.com>; Fri, 01 Feb 2008 10:18:30 -0800 (PST) Date: Fri, 01 Feb 2008 10:18:29 -0800 From: John Plocher Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A34672.6090909@sun.com> Sender: John.Plocher@sun.com To: Petr Sumbera Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A36275.3020201@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> <18339.9551.167704.157019@gargle.gargle.HOWL> <47A34672.6090909@sun.com> User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) Status: RO Content-Length: 587 Petr Sumbera wrote: > James Carlson wrote: >>> http://tomcat.apache.org/connectors-doc/generic_howto/workers.html >> OK; so matching all of this up is "merely" a user configuration >> problem, right? > > Yes. This seems to be a huge architectural hole - things can't work out of the box without the user/admin performing arcane rituals and consulting outside oracles written for non-solaris platforms... If we are serious about delivering a highly integrated and functional SAMP stack, it behooves us to do a better job of integration than this project seems to be doing... -John From carlsonj@phorcys.east.sun.com Fri Feb 1 10:31:12 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m11IVCwv008468 for ; Fri, 1 Feb 2008 10:31:12 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m11IVAeg002101; Fri, 1 Feb 2008 10:31:10 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVK00A0XORY6600@nwk-avmta-2.sfbay.sun.com>; Fri, 01 Feb 2008 10:31:10 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVK002UPORXK5E0@nwk-avmta-2.sfbay.sun.com>; Fri, 01 Feb 2008 10:31:09 -0800 (PST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m11IV9xi011904; Fri, 01 Feb 2008 13:31:09 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.2+Sun/8.14.2/Submit) id m11IV94P011901; Fri, 01 Feb 2008 13:31:09 -0500 (EST) Date: Fri, 01 Feb 2008 13:31:09 -0500 From: James Carlson Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A36275.3020201@Sun.Com> To: John Plocher Cc: Petr Sumbera , PSARC-ext@sun.com, Joseph Kowalski Message-id: <18339.25965.44677.311062@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> <18339.9551.167704.157019@gargle.gargle.HOWL> <47A34672.6090909@sun.com> <47A36275.3020201@Sun.Com> Status: RO Content-Length: 1349 John Plocher writes: > Petr Sumbera wrote: > > James Carlson wrote: > >>> http://tomcat.apache.org/connectors-doc/generic_howto/workers.html > >> OK; so matching all of this up is "merely" a user configuration > >> problem, right? > > > > Yes. > > This seems to be a huge architectural hole - things can't work out of the > box without the user/admin performing arcane rituals and consulting > outside oracles written for non-solaris platforms... > > If we are serious about delivering a highly integrated and functional > SAMP stack, it behooves us to do a better job of integration than this > project seems to be doing... I agree with this, though I don't think it's entirely this project's fault that the configuration mechanism looks like a do-it-yourself toolkit. If I weren't trying to sabbaticalize myself, I might have been moved to say that we need a derail to deliver some advice. I don't know how to make it right, but it certainly seems to me that this needs to be simpler. Perhaps those who use these plug-ins are just used to everything being really hard and don't notice this one problem so much. :-/ -- James Carlson, Solaris Networking 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 From Petr.Sumbera@sun.com Mon Feb 4 00:40:45 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m148eiEL024583 for ; Mon, 4 Feb 2008 00:40:44 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m148eYY4015102 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 4 Feb 2008 16:40:43 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVP0010JHFQJ500@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 00:40:38 -0800 (PST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVP00HL2HFPZJA0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 00:40:37 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m148eaam015157 for ; Mon, 04 Feb 2008 08:40:36 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVP00G01GSL5G00@fe-emea-09.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 08:40:36 +0000 (GMT) Received: from [10.162.37.119] ([85.160.21.75]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVP006GLHFG9610@fe-emea-09.sun.com>; Mon, 04 Feb 2008 08:40:35 +0000 (GMT) Date: Mon, 04 Feb 2008 09:40:27 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A35A5B.7050605@Sun.Com> Sender: Petr.Sumbera@sun.com To: John Plocher Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A6CF7B.4010100@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <47A204DB.7020409@Sun.Com> <47A32262.8020800@sun.com> <47A35A5B.7050605@Sun.Com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 1002 John Plocher wrote: > Petr Sumbera wrote: >> John Plocher wrote: >>> Petr Sumbera wrote: >>>> Tomcat is started (beside manually) via Apache 1.3 init script >>> >>> What about Apache 2.x - how does this work with that version? >> >> Answer is simple. It doesn't work. > > OK, but... > >> >> Tomcat was introduced when there was no Apache 2. Tomcat is located in >> Apache 1.3 subdirectory (usr/apache) and not in Apache 2 subdirectory >> (usr/apache2). >> >> But still it can be manually configured and run as stand-alone server >> or to communicate with Apache 2. The best way is probably to reuse >> /etc/init.d/apache. >> >> For Apache 2.2 (in Nevada) there is by default mod_proxy_ajp.so which >> communicates via AJP13 protocol. While for Apache 2.0 (Solaris 10) >> mod_jk has to be compiled. > > > ... here you say that it *does* work. I'm confused. What do I need to > do if I run Apache2 and wish to use tomcat5.5? It's do it yourself task. But it doesn't work out of box. Petr From Petr.Sumbera@sun.com Mon Feb 4 00:47:34 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m148lXOD024643 for ; Mon, 4 Feb 2008 00:47:33 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m148lNhb017848 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 4 Feb 2008 16:47:32 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVP0020XHR7G500@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 00:47:31 -0800 (PST) Received: from gmp-eb-mail-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVP00ESTHR5PP70@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 00:47:29 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m148lSUH027992 for ; Mon, 04 Feb 2008 08:47:28 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVP00D01HIA5H00@fe-emea-09.sun.com> (original mail from Petr.Sumbera@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 08:47:28 +0000 (GMT) Received: from [10.162.37.119] ([85.160.21.75]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVP0064SHQK9640@fe-emea-09.sun.com>; Mon, 04 Feb 2008 08:47:10 +0000 (GMT) Date: Mon, 04 Feb 2008 09:47:08 +0100 From: Petr Sumbera Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A36275.3020201@Sun.Com> Sender: Petr.Sumbera@sun.com To: John Plocher Cc: James Carlson , PSARC-ext@sun.com, Joseph Kowalski Message-id: <47A6D10C.5070204@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> <18339.9551.167704.157019@gargle.gargle.HOWL> <47A34672.6090909@sun.com> <47A36275.3020201@Sun.Com> User-Agent: Thunderbird 2.0.0.6 (X11/20071105) Status: RO Content-Length: 775 John Plocher wrote: > Petr Sumbera wrote: >> James Carlson wrote: >>>> http://tomcat.apache.org/connectors-doc/generic_howto/workers.html >>> OK; so matching all of this up is "merely" a user configuration >>> problem, right? >> >> Yes. > > This seems to be a huge architectural hole - things can't work out of the > box without the user/admin performing arcane rituals and consulting > outside oracles written for non-solaris platforms... > > If we are serious about delivering a highly integrated and functional > SAMP stack, it behooves us to do a better job of integration than this > project seems to be doing... I believe that WEBstack team has Tomcat on their road map. This particular case is to handle security vulnerabilities in Solaris 10 and 9 Tomcat. Petr From Darren.Moffat@sun.com Mon Feb 4 08:32:02 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m14GW18s006859 for ; Mon, 4 Feb 2008 08:32:01 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m14GVqeb025218 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 5 Feb 2008 00:32:00 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVQ00A0Z39APQ00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 09:31:58 -0700 (MST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVQ0065J36OTU40@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 09:30:37 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m14GUOKY007978 for ; Mon, 04 Feb 2008 16:30:24 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVQ009011KN9600@fe-emea-09.sun.com> (original mail from Darren.Moffat@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 04 Feb 2008 16:30:24 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVQ00I8Z362H920@fe-emea-09.sun.com>; Mon, 04 Feb 2008 16:30:04 +0000 (GMT) Date: Mon, 04 Feb 2008 16:30:02 +0000 From: Darren J Moffat Subject: Re: Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008] In-reply-to: <47A31C83.1020702@sun.com> Sender: Darren.Moffat@sun.com To: Petr Sumbera Cc: James Carlson , Joseph Kowalski , PSARC-ext@sun.com Message-id: <47A73D8A.2050003@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200801310045.m0V0jAYr002609@train1.eng.sun.com> <18337.53489.519274.517174@gargle.gargle.HOWL> <47A1EFDA.8020208@sun.com> <18337.64926.71792.335314@gargle.gargle.HOWL> <47A31C83.1020702@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20080102) Status: RO Content-Length: 666 Petr Sumbera wrote: > 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". We used to have just /usr/apache2 now we have /usr/apache2/2.2 and SMF service instances :apache2 and :apache22. I think the same should be done for Tomcat, ie tomcat55 in this case, based on my past exposure to it and the other comments in this case about needing to know exactly which version of Tomcat you are dealing with. Also experience from JDK's should tell us that we should, sadly, be as specific as we can. -- Darren J Moffat