From petede@sac.sfbay.sun.com Wed Dec 9 08:57:38 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nB9GvcVF025350 for ; Wed, 9 Dec 2009 08:57:38 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nB9GvctX001347; Wed, 9 Dec 2009 08:57:38 -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 <0KUE0030T9S2TW00@nwk-avmta-2.sfbay.sun.com>; Wed, 09 Dec 2009 08:57:38 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUE0000J9S1QZ40@nwk-avmta-2.sfbay.sun.com>; Wed, 09 Dec 2009 08:57:37 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nB9GvaDm011488; Wed, 09 Dec 2009 08:57:36 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nB9GvZRb025345; Wed, 09 Dec 2009 08:57:35 -0800 (PST) Received: (from petede@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id nB9GvZPB025341; Wed, 09 Dec 2009 08:57:35 -0800 (PST) Date: Wed, 09 Dec 2009 08:57:35 -0800 (PST) From: Peter Dennis Subject: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] To: PSARC-ext@sun.com Cc: petr.sumbera@sun.com Message-id: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 1832 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: EOF Apache JServ 1.2. Name of Document Author/Supplier: Author: Petr Sumbera 1.3 Date of This Document: 09 December, 2009 4. Technical Description EOF Apache JServ ---------------- The Apache JServ support for Apache Web Server 1.3 (PSARC/2000/040) is now completely redundant and has been obsoleted by community. There is a fully functional alternative for Apache JServ in Solaris which is Apache Tomcat with Apache web server JK module (PSARC/2008/711). The Apache JServ project is no longer developed and it has not been touched since January 2001. This project completely removes support for Apache JServ from Solaris Nevada/OpenSolaris. Components to be removed /usr/apache/libexec/ mod_jserv.so ApacheJServ.jar jsdk.jar /usr/apache/jserv/docs/ /etc/apache/ jserv.conf jserv.properties zone.properties /var/apache/servlets/ /var/apache/logs/ mod_jserv.log Typical migration path consist of creating new web application directory subtree for Apache Tomcat /var/tomcat/webapps/[MigratedAPP]/ (including /WEB-INF/web.xml descriptor file), copying of Java class files from Apache JServ installation (/var/apache/servlets/) to new subtree (/WEB-INF/classes/) and finally Apache Web server and Tomcat configuration. Note: Apache JServ applications which are using some vendor specific hooks or applications with some incompatibilities between servlet version specifications (Apache JServ: v2.0, Tomcat: v2.5), might need some code changes. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From gdamore@sun.com Wed Dec 9 09:34:30 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nB9HYUpG028307 for ; Wed, 9 Dec 2009 09:34:30 -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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nB9HYTDI006159 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 9 Dec 2009 09:34:30 -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 <0KUE0011VBHH3K00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 09 Dec 2009 10:34:29 -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 <0KUE00H6FBHGQK80@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 09 Dec 2009 10:34:29 -0700 (MST) 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 nB9HYS80021574 for ; Wed, 09 Dec 2009 09:34:28 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUE00A009DXMP00@fe-sfbay-10.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 09 Dec 2009 09:34:28 -0800 (PST) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUE00JQXBHGUZA0@fe-sfbay-10.sun.com>; Wed, 09 Dec 2009 09:34:28 -0800 (PST) Date: Wed, 09 Dec 2009 09:34:27 -0800 From: "Garrett D'Amore" Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> Sender: Garrett.Damore@sun.com To: Peter Dennis Cc: PSARC-ext@sun.com, Petr.Sumbera@sun.com Message-id: <4B1FDFA3.3070603@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 3364 Architecturally, this sounds like a good thing. My main concerns here really relate to notification of potential vendors and consumers. While that's not architectural (its a C-Team issue), its still interesting. Do we have any sense of who's using these features. Note that PSARC 2000/040 specified the jserv files as Stable. Personally, I think this was probably in error, given that it was tracking an open source effort without a proven track record. I believe this EOF therefore requires some "extra effort" to ensure that no negative impacts are felt within the software we ship, that there is extra effort made to inform users of this impending EOF, and that the project team has made a good faith effort to identify what external consumers, if any, are going to be busted by this. (A brief bit of googling on my part suggests that there has already been a fair amount of "communication" about mod_jserv being "deprecated" done by the Apache community. In fact, it would appear that Apache 2.x does not support this.) Indeed, this begs a question: wouldn't it simply be easier to remove mod_jserv with the removal of Apache 1.3.x. I'm assuming that if we've not already EOF'd Apache 1.3 in favor of 2.0, that we will do so at some point in the future? Btw, I'm assuming this is meant for Minor binding, as its not appropriate IMO for a Patch release. - Garrett Peter Dennis wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > EOF Apache JServ > 1.2. Name of Document Author/Supplier: > Author: Petr Sumbera > 1.3 Date of This Document: > 09 December, 2009 > 4. Technical Description > EOF Apache JServ > ---------------- > > The Apache JServ support for Apache Web Server 1.3 (PSARC/2000/040) is > now completely redundant and has been obsoleted by community. There > is a fully functional alternative for Apache JServ in Solaris which > is Apache Tomcat with Apache web server JK module (PSARC/2008/711). > The Apache JServ project is no longer developed and it has not been > touched since January 2001. > > This project completely removes support for Apache JServ from Solaris > Nevada/OpenSolaris. > > Components to be removed > > /usr/apache/libexec/ > mod_jserv.so > ApacheJServ.jar > jsdk.jar > /usr/apache/jserv/docs/ > /etc/apache/ > jserv.conf > jserv.properties > zone.properties > /var/apache/servlets/ > /var/apache/logs/ > mod_jserv.log > > Typical migration path consist of creating new web application directory > subtree for Apache Tomcat /var/tomcat/webapps/[MigratedAPP]/ (including > /WEB-INF/web.xml descriptor file), copying of Java class files from > Apache JServ installation (/var/apache/servlets/) to new subtree > (/WEB-INF/classes/) and finally Apache Web server and Tomcat configuration. > > Note: Apache JServ applications which are using some vendor specific > hooks or applications with some incompatibilities between servlet > version specifications (Apache JServ: v2.0, Tomcat: v2.5), might > need some code changes. > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > From Petr.Sumbera@Sun.COM Thu Dec 10 01:35:19 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBA9ZJ2h002276 for ; Thu, 10 Dec 2009 01:35:19 -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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBA9ZJfA023486 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 10 Dec 2009 01:35:19 -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 <0KUF00B03JYVJR00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 02:35:19 -0700 (MST) Received: from gmp-eb-inf-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 <0KUF008CUJYUIK10@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 02:35:19 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBA9ZICb002352 for ; Thu, 10 Dec 2009 09:35:18 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUF00500IVZDQ00@fe-emea-09.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 09:35:01 +0000 (GMT) Received: from [129.157.71.67] ([unknown] [129.157.71.67]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUF00G0IJY7R6C0@fe-emea-09.sun.com>; Thu, 10 Dec 2009 09:34:56 +0000 (GMT) Date: Thu, 10 Dec 2009 10:34:52 +0100 From: Petr Sumbera Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B1FDFA3.3070603@sun.com> Sender: Petr.Sumbera@Sun.COM To: "Garrett D'Amore" Cc: Peter Dennis , PSARC-ext@Sun.COM Message-id: <4B20C0BC.8080201@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090908) Status: RO Content-Length: 1854 Garrett D'Amore wrote: > Architecturally, this sounds like a good thing. My main concerns here > really relate to notification of potential vendors and consumers. While > that's not architectural (its a C-Team issue), its still interesting. > Do we have any sense of who's using these features. Not sure here. We got recently one escalation for S10 which made us to act. But it was probably first since S10 was released. > Note that PSARC 2000/040 specified the jserv files as Stable. > Personally, I think this was probably in error, given that it was > tracking an open source effort without a proven track record. I > believe this EOF therefore requires some "extra effort" to ensure that > no negative impacts are felt within the software we ship, that there is > extra effort made to inform users of this impending EOF, and that the > project team has made a good faith effort to identify what external > consumers, if any, are going to be busted by this. Agree. Will ask SFW C-Team to double check. > (A brief bit of googling on my part suggests that there has already been > a fair amount of "communication" about mod_jserv being "deprecated" done > by the Apache community. In fact, it would appear that Apache 2.x does > not support this.) > Indeed, this begs a question: wouldn't it simply be easier to remove > mod_jserv with the removal of Apache 1.3.x. I'm assuming that if we've > not already EOF'd Apache 1.3 in favor of 2.0, that we will do so at some > point in the future? Simple removal of JServ seemed to be easier, faster and less controversial. So that question of EOF Apache 1.3 is beyond this case. But yes there are from time to time some discussions which might lead to it. > Btw, I'm assuming this is meant for Minor binding, as its not > appropriate IMO for a Patch release. Correct. Petr From gdamore@sun.com Thu Dec 10 07:57:53 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBAFvrTf008392 for ; Thu, 10 Dec 2009 07:57:53 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBAFvqLE022033 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 10 Dec 2009 09:57:53 -0600 (CST) 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 <0KUG0070J1OHJI00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 07:57:53 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUG00EJW1OEC480@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 07:57:50 -0800 (PST) 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 nBAFvoPQ029309 for ; Thu, 10 Dec 2009 07:57:50 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUG006001BBHP00@fe-sfbay-09.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 07:57:50 -0800 (PST) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUG00G9H1O8MP70@fe-sfbay-09.sun.com>; Thu, 10 Dec 2009 07:57:49 -0800 (PST) Date: Thu, 10 Dec 2009 07:57:44 -0800 From: "Garrett D'Amore" Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B20C0BC.8080201@sun.com> Sender: Garrett.Damore@sun.com To: Petr Sumbera Cc: Peter Dennis , PSARC-ext@sun.com Message-id: <4B211A78.2060008@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> <4B20C0BC.8080201@sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 2314 Petr Sumbera wrote: > Garrett D'Amore wrote: >> Architecturally, this sounds like a good thing. My main concerns >> here really relate to notification of potential vendors and >> consumers. While that's not architectural (its a C-Team issue), its >> still interesting. Do we have any sense of who's using these features. > > Not sure here. We got recently one escalation for S10 which made us to > act. But it was probably first since S10 was released. > >> Note that PSARC 2000/040 specified the jserv files as Stable. >> Personally, I think this was probably in error, given that it was >> tracking an open source effort without a proven track record. I >> believe this EOF therefore requires some "extra effort" to ensure >> that no negative impacts are felt within the software we ship, that >> there is extra effort made to inform users of this impending EOF, and >> that the project team has made a good faith effort to identify what >> external consumers, if any, are going to be busted by this. > > Agree. Will ask SFW C-Team to double check. Thanks. >> Indeed, this begs a question: wouldn't it simply be easier to remove >> mod_jserv with the removal of Apache 1.3.x. I'm assuming that if >> we've not already EOF'd Apache 1.3 in favor of 2.0, that we will do >> so at some point in the future? > > Simple removal of JServ seemed to be easier, faster and less > controversial. So that question of EOF Apache 1.3 is beyond this case. > But yes there are from time to time some discussions which might lead > to it. I'm not sure that its much less controversial for Solaris Nevada/Next. It seems like EOF of 1.3 is something that ought to occur at about this time, and that the time is ripe for it. (Apache has both Apache 2.0 and Apache 2.2 as release trains available at this time -- so 1.3 is actually two releases behind schedule -- continuing to ship it makes about as much sense as continuing to ship Gnome 1.x -- actually less since ISV software generally doesn't dynamically link against the Apache server.) I think personally, I'd rather go through just a single EOF process than go through two of them. > >> Btw, I'm assuming this is meant for Minor binding, as its not >> appropriate IMO for a Patch release. > > Correct. Ok. -- Garrett > > Petr From Petr.Sumbera@Sun.COM Thu Dec 10 08:50:06 2009 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 nBAGo6NN009310 for ; Thu, 10 Dec 2009 08:50:06 -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.4) with ESMTP id nBAGo6n8006128 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 10 Dec 2009 09:50:06 -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 <0KUG0082N43IU700@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 09:50:06 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUG00GAV43HDED0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 09:50:06 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBAGo4iC008281 for ; Thu, 10 Dec 2009 16:50:05 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUG00C000WYBO00@fe-emea-10.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 16:50:01 +0000 (GMT) Received: from [129.157.71.67] ([unknown] [129.157.71.67]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUG00BZS439HZB0@fe-emea-10.sun.com>; Thu, 10 Dec 2009 16:49:57 +0000 (GMT) Date: Thu, 10 Dec 2009 17:49:53 +0100 From: Petr Sumbera Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B211A78.2060008@sun.com> Sender: Petr.Sumbera@Sun.COM To: "Garrett D'Amore" Cc: Peter Dennis , PSARC-ext@Sun.COM Message-id: <4B2126B1.1040705@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> <4B20C0BC.8080201@sun.com> <4B211A78.2060008@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090908) Status: RO Content-Length: 1523 Garrett D'Amore wrote: >>> Indeed, this begs a question: wouldn't it simply be easier to remove >>> mod_jserv with the removal of Apache 1.3.x. I'm assuming that if >>> we've not already EOF'd Apache 1.3 in favor of 2.0, that we will do >>> so at some point in the future? >> >> Simple removal of JServ seemed to be easier, faster and less >> controversial. So that question of EOF Apache 1.3 is beyond this case. >> But yes there are from time to time some discussions which might lead >> to it. > > I'm not sure that its much less controversial for Solaris > Nevada/Next. It seems like EOF of 1.3 is something that ought to > occur at about this time, and that the time is ripe for it. (Apache has > both Apache 2.0 and Apache 2.2 as release trains available at this time > -- so 1.3 is actually two releases behind schedule -- continuing to ship > it makes about as much sense as continuing to ship Gnome 1.x -- actually > less since ISV software generally doesn't dynamically link against the > Apache server.) > > I think personally, I'd rather go through just a single EOF process than > go through two of them. There used to be some vendor specific Apache 1.3 modules (e.g. from Oracle, IBM). I'm not sure whether all these have their equivalent for Apache 2.2 now. So with all respect to Gnome I wouldn't compare it here. This case is here so we can remove Apache JServ as soon as possible since there is clear migration path. While Apache 1.3 removal would require usual time off. Petr From gdamore@sun.com Thu Dec 10 08:58:11 2009 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 nBAGwA7C009667 for ; Thu, 10 Dec 2009 08:58:10 -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.4) with ESMTP id nBAGw9lp012238 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 10 Dec 2009 09:58:10 -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 <0KUG0030L4GXFO00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 08:58:09 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUG00JLL4GXM8B0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 08:58:09 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBAGw4LB027332 for ; Thu, 10 Dec 2009 08:58:04 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUG00700346KN00@fe-sfbay-09.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Thu, 10 Dec 2009 08:58:04 -0800 (PST) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUG001I14GRYVD0@fe-sfbay-09.sun.com>; Thu, 10 Dec 2009 08:58:03 -0800 (PST) Date: Thu, 10 Dec 2009 08:58:02 -0800 From: "Garrett D'Amore" Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B2126B1.1040705@sun.com> Sender: Garrett.Damore@sun.com To: Petr Sumbera Cc: Peter Dennis , PSARC-ext@sun.com Message-id: <4B21289A.8080609@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> <4B20C0BC.8080201@sun.com> <4B211A78.2060008@sun.com> <4B2126B1.1040705@sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 2462 Petr Sumbera wrote: > Garrett D'Amore wrote: >>>> Indeed, this begs a question: wouldn't it simply be easier to >>>> remove mod_jserv with the removal of Apache 1.3.x. I'm assuming >>>> that if we've not already EOF'd Apache 1.3 in favor of 2.0, that we >>>> will do so at some point in the future? >>> >>> Simple removal of JServ seemed to be easier, faster and less >>> controversial. So that question of EOF Apache 1.3 is beyond this >>> case. But yes there are from time to time some discussions which >>> might lead to it. >> >> I'm not sure that its much less controversial for Solaris >> Nevada/Next. It seems like EOF of 1.3 is something that ought to >> occur at about this time, and that the time is ripe for it. (Apache >> has both Apache 2.0 and Apache 2.2 as release trains available at >> this time -- so 1.3 is actually two releases behind schedule -- >> continuing to ship it makes about as much sense as continuing to ship >> Gnome 1.x -- actually less since ISV software generally doesn't >> dynamically link against the Apache server.) >> >> I think personally, I'd rather go through just a single EOF process >> than go through two of them. > > There used to be some vendor specific Apache 1.3 modules (e.g. from > Oracle, IBM). I'm not sure whether all these have their equivalent for > Apache 2.2 now. So with all respect to Gnome I wouldn't compare it here. > > This case is here so we can remove Apache JServ as soon as possible > since there is clear migration path. While Apache 1.3 removal would > require usual time off. Gosh, I'd hope that vendors would have made version 2.x modules available. Apache 2.0 was released quite some time ago... back in 2002. This is no longer cutting edge technology. (Apache 1.3 was released back in 1998.) That said, I'm happy to +1 this case if an EOF of Apache 1.3 is not deemed practical at this time. I do think the project team should at least undertake the effort to Obsolete Apache 1.3 as soon as possible though, so we can start the timer for its actual removal. (Actually, getting a notification in the the next S10 update would allow removal in the next full release, assuming you get buy in from the various committees that would have to approve it. It seems like that approval would be fairly straight-forward to get, unless there are known consumers that we have to support and which can't migrate to Apache 2.0 or Apache 2.2.) - Garrett From Petr.Sumbera@sun.com Thu Dec 10 09:08:33 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBAH8WVL010091 for ; Thu, 10 Dec 2009 09:08:32 -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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBAH8Wod023007 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 10 Dec 2009 09:08: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 <0KUG00K0H4Y7GY00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 10 Dec 2009 09:08:31 -0800 (PST) Received: from gmp-eb-inf-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 <0KUG00K724Y48S10@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 10 Dec 2009 09:08:29 -0800 (PST) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBAH8SRf010438 for ; Thu, 10 Dec 2009 17:08:28 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUG000004IY3800@fe-emea-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 10 Dec 2009 17:08:28 +0000 (GMT) Received: from [129.157.71.67] ([unknown] [129.157.71.67]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUG0002A4XZ7X60@fe-emea-10.sun.com>; Thu, 10 Dec 2009 17:08:23 +0000 (GMT) Date: Thu, 10 Dec 2009 18:08:19 +0100 From: Petr Sumbera Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B21289A.8080609@sun.com> Sender: Petr.Sumbera@sun.com To: "Garrett D'Amore" Cc: Peter Dennis , PSARC-ext@sun.com Message-id: <4B212B03.4070705@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> <4B20C0BC.8080201@sun.com> <4B211A78.2060008@sun.com> <4B2126B1.1040705@sun.com> <4B21289A.8080609@sun.com> User-Agent: Thunderbird 2.0.0.22 (X11/20090908) Status: RO Content-Length: 1697 Garrett D'Amore wrote: > Petr Sumbera wrote: >> Garrett D'Amore wrote: >>> I think personally, I'd rather go through just a single EOF process >>> than go through two of them. >> >> There used to be some vendor specific Apache 1.3 modules (e.g. from >> Oracle, IBM). I'm not sure whether all these have their equivalent for >> Apache 2.2 now. So with all respect to Gnome I wouldn't compare it here. >> >> This case is here so we can remove Apache JServ as soon as possible >> since there is clear migration path. While Apache 1.3 removal would >> require usual time off. > > Gosh, I'd hope that vendors would have made version 2.x modules > available. Apache 2.0 was released quite some time ago... back in > 2002. This is no longer cutting edge technology. We have now in Nevada just Apache 2.2 (not 2.0). Note also that modules are not binary compatible between version 2.0 and 2.2. > (Apache 1.3 was released back in 1998.) > > That said, I'm happy to +1 this case if an EOF of Apache 1.3 is not > deemed practical at this time. I do think the project team should at > least undertake the effort to Obsolete Apache 1.3 as soon as possible > though, so we can start the timer for its actual removal. > > (Actually, getting a notification in the the next S10 update would allow > removal in the next full release, assuming you get buy in from the > various committees that would have to approve it. It seems like that > approval would be fairly straight-forward to get, unless there are known > consumers that we have to support and which can't migrate to Apache 2.0 > or Apache 2.2.) I'm ok with this. My manager has this on his to do list now for some time. Petr From Peter.Dennis@sun.com Thu Dec 17 02:22:27 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBHAMQ3v000025 for ; Thu, 17 Dec 2009 02:22:26 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBHAMPnh012659 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 17 Dec 2009 04:22:26 -0600 (CST) 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 <0KUS00G0XKTDSF00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Dec 2009 03:22:25 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUS00KCOKTCI1B0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Dec 2009 03:22:24 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBHAMNoT013951 for ; Thu, 17 Dec 2009 10:22:23 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUS00800K1K4X00@fe-emea-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Dec 2009 10:22:20 +0000 (GMT) Received: from [129.156.198.33] ([unknown] [129.156.198.33]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUS00CRZKT2IM20@fe-emea-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 17 Dec 2009 10:22:14 +0000 (GMT) Date: Thu, 17 Dec 2009 10:22:14 +0000 From: Peter Dennis - Sustaining Engineer Subject: Re: EOF Apache JServ [PSARC/2009/672 FastTrack timeout 12/16/2009] In-reply-to: <4B212B03.4070705@sun.com> Sender: Peter.Dennis@sun.com To: Petr Sumbera Cc: PSARC-ext@sun.com Message-id: <4B2A0656.7070000@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912091657.nB9GvZPB025341@sac.sfbay.sun.com> <4B1FDFA3.3070603@sun.com> <4B20C0BC.8080201@sun.com> <4B211A78.2060008@sun.com> <4B2126B1.1040705@sun.com> <4B21289A.8080609@sun.com> <4B212B03.4070705@sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091124) Status: RO Content-Length: 76 This fast track was approved during the PSARC meeting on 16-Dec-2009. Pete