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 <[email protected]
> wrote:
> > -----Original Message-----
> > From: Jeffrey Janner [mailto:[email protected]]
> > 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:[email protected]]
> > > 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: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
