Return-Path: 
 <common-issues-return-43380-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8B95CE6E2
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Fri,  1 Feb 2013 19:36:13 +0000 (UTC)
Received: (qmail 11833 invoked by uid 500); 1 Feb 2013 19:36:13 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 11754 invoked by uid 500); 1 Feb 2013 19:36:13 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 11745 invoked by uid 99); 1 Feb 2013 19:36:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 19:36:13 +0000
Date: Fri, 1 Feb 2013 19:36:13 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12628350.1358553652667.231017.1359747373141@arcas>
In-Reply-To: <JIRA.12628350.1358553652667@arcas>
References: <JIRA.12628350.1358553652667@arcas>
Subject: [jira] [Commented] (HADOOP-9244) Upgrade servlet-api dependency
 from version 2.5 to 3.0.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HADOOP-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569003#comment-13569003 ] 

Suresh Srinivas commented on HADOOP-9244:
-----------------------------------------

bq. Looks like the consensus is not to upgrade the jetty in branch-2. So, shall we move forward with Jetty8 and servlet3 in the trunk?
+1

Does any one know performance comparison of Jetty 8 with that of Jetty 6? During WebHDFS work, performance analysis indicated poor performance/latency in http layers (did not spend too much confirming the same). I was interested in seeing if later versions of Jetty would result in better performance. Given that Jetty is becoming critical not only for REST APIs, but also for data paths, understanding the performance gains/losses would be great.
                
> Upgrade servlet-api dependency from version 2.5 to 3.0.
> -------------------------------------------------------
>
>                 Key: HADOOP-9244
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9244
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.0.3-alpha
>            Reporter: Plamen Jeliazkov
>            Assignee: Plamen Jeliazkov
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: HDFS-4422.patch
>
>
> Please update the servlet-api jar from 2.5 to javax.servlet 3.0 via Maven:
> <dependency>
>         <groupId>javax.servlet</groupId>
>         <artifactId>javax.servlet-api</artifactId>
>         <version>3.0.1</version>
>         <scope>provided</scope>
> </dependency>
> I am running a 2.0.3 dev-cluster and can confirm compatibility. I have removed the servlet-api-2.5.jar file and replaced it with javax.servlet-3.0.jar file. I am using javax.servlet-3.0 because it implements methods that I use for a filter, namely the HttpServletResponse.getStatus() method.
> I believe it is a gain to have this dependency as it allows more functionality and has so far proven to be backwards compatible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira