Return-Path: 
 <users-return-236558-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
X-Original-To: apmail-tomcat-users-archive@www.apache.org
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 56505D672
	for <apmail-tomcat-users-archive@www.apache.org>;
 Wed, 12 Sep 2012 05:30:14 +0000 (UTC)
Received: (qmail 79703 invoked by uid 500); 12 Sep 2012 05:30:10 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 79584 invoked by uid 500); 12 Sep 2012 05:30:09 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 79547 invoked by uid 99); 12 Sep 2012 05:30:09 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2012 05:30:09 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of adisinha0423@gmail.com
 designates 209.85.223.173 as permitted sender)
Received: from [209.85.223.173] (HELO mail-ie0-f173.google.com)
 (209.85.223.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Sep 2012 05:30:02 +0000
Received: by iebc10 with SMTP id c10so2894756ieb.18
        for <users@tomcat.apache.org>; Tue, 11 Sep 2012 22:29:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=cpEh0cQ7QNoA7wH4qef66TpgriUVKM/1005QbC3glhE=;
        b=WTdxMBJtcRkuo8sgPU3iOTX71c0w/irJIArHoRlAC2ka60PLHz8So2Mx25neNl7FxG
         vFvPil7ytviHgMy3ilVY5JzYkQBDCVV3jvNAbJYUPkDtFTP9++5fNYxCERnRP7pQhfYu
         Wbx/r15VuAf4Vs9rArj5VpoSLHxCLvU98k1bdpjdy5IR7P5mS+35u7KYv5A17wrNy51/
         TDprr6QU0n4pNo+UOotYGATz8kzp/6e8iZW7GuKtvAvnOD7kBp7ZprIc/0SMZB+6YT67
         Ovq3xhaStiKdsgWN3oHlgHODaOfT8jkBInJ+0U0yeGv+M8hMHFCi2QgTGMKpDi4hR8fK
         bzwA==
MIME-Version: 1.0
Received: by 10.50.202.4 with SMTP id ke4mr19681831igc.72.1347427780959; Tue,
 11 Sep 2012 22:29:40 -0700 (PDT)
Received: by 10.231.188.92 with HTTP; Tue, 11 Sep 2012 22:29:40 -0700 (PDT)
In-Reply-To: 
 <7215BA462D00D343B2837F9113F0131F01277E32B9@POSTOFFICE02.polydyne.com>
References: 
 <CAJjyRMfoxpVNR-YwhCTqCfiOBtCi5NgJXiw=MeN5uR6fd+hjmg@mail.gmail.com>
	<7215BA462D00D343B2837F9113F0131F01277E32A5@POSTOFFICE02.polydyne.com>
	<7215BA462D00D343B2837F9113F0131F01277E32B9@POSTOFFICE02.polydyne.com>
Date: Wed, 12 Sep 2012 10:59:40 +0530
Message-ID: 
 <CAJjyRMcCQmtb61bW+unbHrj=5-mfh9H8=n0bsgOiHVa0tCW7Vg@mail.gmail.com>
Subject: Re: HTTP NIO connector not supporting IPv6
From: Aditi Sinha <adisinha0423@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=f46d044788433e9e4f04c97a7a0c

--f46d044788433e9e4f04c97a7a0c
Content-Type: text/plain; charset=ISO-8859-1

Thanks Dan, Jeff.



There are no errors in catalina.log file.

The connector tags are defined as below in server.xml. This configuration
does not support IPv6.



  <Connector port="8080" protocol="*HTTP/1.1*" connectionTimeout="20000"
redirectPort="8443" />



  <Connector port="8443" protocol="*
org.apache.coyote.http11.Http11NioProtocol*" SSLEnabled="true"
maxThreads="150"

      scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"
keystoreFile="xxxxxx" keystorePass="xxxxxx"/>







Below configuration supports IPv6. The only difference is the protocol.



  <Connector port="8080" protocol="*org.apache.coyote.http11.Http11Protocol*"
connectionTimeout="20000" redirectPort="8443" />



  <Connector port="8443" protocol="*org.apache.coyote.http11.Http11Protocol*"
SSLEnabled="true" maxThreads="150"

      scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"
keystoreFile="xxxxxx" keystorePass="xxxxxx"/>



 Please let me know if something missing here?



Thanks & Regards,

Aditi


On Tue, Sep 11, 2012 at 7:30 PM, Jeffrey Janner <Jeffrey.Janner@polydyne.com
> wrote:

> > -----Original Message-----
> > From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
> > Sent: Tuesday, September 11, 2012 8:57 AM
> > To: 'Tomcat Users List'
> > Subject: RE: HTTP NIO connector not supporting IPv6
> >
> > Aditi -
> >
> > All connectors support both IPv4 and IPv6, including BIO, NIO, and
> > native/APR. However, how you configure the connector will affect which
> > protocol is supported.
> >
> > As far as I've been able to tell from empirical testing (see previous
> > threads), if you leave off the address parameter, the java-based
> > connectors (BIO & NIO) will set up listeners on both of the "any"
> > addresses, i.e. 0.0.0.0:port for IPv4 and [::]:port for IPv6. Unless
> > it's been fixed in a recent release, the APR will only set up to listen
> > on the IPv6 address.  You have to specifically give it the IPv4 "any"
> > if you want IPv4 support. Since I only support IPv4 right now, I
> > haven't re-tested the current version of APR. (pltr)
> >
> > So, as Daniel says, please resend your message with copies of the
> > actual <connector> tags, minus any passwords and excess comments.  If
> > you are seeing any errors in your catalina.log file, those would be
> > helpful as well.
> >
> > Jeff
> >
>
> p.s. sorry for the top-post, it's early.
> p.p.s.  The above is testing done under Windows servers.
>
> Also, you really should upgrade to the latest sun JDK (jdk1.6.0_35).
>  There are issues with some of the lower versions, but I don't think any
> that affect the connector mechanism.
>
>
> > > -----Original Message-----
> > > From: Aditi Sinha [mailto:adisinha0423@gmail.com]
> > > Sent: Tuesday, September 11, 2012 7:21 AM
> > > To: Tomcat Users List
> > > Subject: HTTP NIO connector not supporting IPv6
> > >
> > > Hi,
> > >
> > >
> > >
> > > We have a web server hosted on Apache Tomcat Version 7.0.22.
> > >
> > > Machine details: Windows 2008 server machine, 32-bit OS
> > >
> > > Java version:  jdk1.6.0_25
> > >
> > >
> > >
> > > Two HTTP connectors are defined in server.xml.
> > >
> > > 1.       For non-SSL requests:  Connector with  protocol="HTTP/1.1"
> > >     (HTTP
> > > BIO connector)
> > >
> > > 2.       For SSL requests:  Connector with
> > > protocol="org.apache.coyote.http11.Http11NioProtocol"       (HTTP NIO
> > > connector)
> > >
> > >
> > >
> > > With the above configuration server is not accessible through the
> > IPv6
> > > address.   The "netstat -an" command also does not list the connector
> > > ports(defined in server.xml).
> > >
> > >
> > >
> > > *On modifying these two connectors to use the BIO implementation,
> > > protocol="org.apache.coyote.http11.Http11Protocol"
> > > the server supports IPv6.  *
> > >
> > >
> > >
> > > Any idea why HTTP NIO connector would not support IPv6?
> > >
> > >
> > >
> > > Thanks & Regards,
> > >
> > > Aditi
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--f46d044788433e9e4f04c97a7a0c--