You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Aditi Sinha <ad...@gmail.com> on 2012/09/11 14:21:07 UTC
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
Re: HTTP NIO connector not supporting IPv6
Posted by Daniel Mikusa <dm...@vmware.com>.
On Sep 11, 2012, at 8:21 AM, Aditi Sinha wrote:
> 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.
Please include the full configuration for your two connectors, or better yet include your entire server.xml (minus comments).
>
> 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).
What is the output of "netstat -an"? Can you include that as well?
Dan
>
>
>
> *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
Re: HTTP NIO connector not supporting IPv6
Posted by Aditi Sinha <ad...@gmail.com>.
Thanks Dan, Jeff for sharing so much of infomation.
I will try the below option and share the result.
Try upgrading from 1.6.0_25 to 1.6.0_35.
Thanks & Regards,
Aditi
On Thu, Sep 13, 2012 at 7:39 PM, Jeffrey Janner <Jeffrey.Janner@polydyne.com
> wrote:
> > -----Original Message-----
> > From: Daniel Mikusa [mailto:dmikusa@vmware.com]
> > Sent: Wednesday, September 12, 2012 2:14 PM
> > To: Tomcat Users List
> > Subject: Re: HTTP NIO connector not supporting IPv6
> >
> > On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
> >
> > >> -----Original Message-----
> > >> From: Daniel Mikusa [mailto:dmikusa@vmware.com]
> > >> Sent: Wednesday, September 12, 2012 10:00 AM
> > >> To: Tomcat Users List
> > >> Subject: Re: HTTP NIO connector not supporting IPv6
> > >>
> > >> On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
> > >>
> > >>> 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"/>
> > >>>
> > >>
> > >> Tried it on my MBP (10.7 w/Java 1.6.0_35) and it worked fine. Tried
> > >> on Windows XP (only version I have available) w/ Java 1.6.0_35 and
> > >> was able to replicate the problem behavior. According to the
> > >> following bug report this is a limitation of the OS / JVM. Looks
> > >> like a recent versions of Windows and a recent version of the JVM
> > are
> > >> required to resolve this.
> > >>
> > >> Try upgrading from 1.6.0_25 to 1.6.0_35.
> > >>
> > >> http://bugs.sun.com/view_bug.do?bug_id=6230761
> > >>
> > >> Dan
> > >>
> > > One workaround is to explicitly define the IPv4 and IPv6 addressing
> > in the <connector>.
> > > That is, add address="0.0.0.0" for any IPv4 connectors and
> > > address="[::]" for any IPv6 connectors. (Or use your real addresses
> > instead of the "any" addresses listed here.) This means setting up 2
> > sets of connectors for each port/protocol, but there's nothing wrong
> > with being explicit.
> > > This is what I had to do to get the APR protocol to set up for IPv4.
> >
> >
> > With all due respect, I do not think that this is going to work for the
> > poster. You're saying that your workaround was for an issue with the
> > APR connector, but the poster is using the NIO connector. The APR
> > connector does not use NIO or the JVM, so I don't think your workaround
> > is relevant. In fact I tried your workaround previously without
> > success. The problem is that on older versions of Windows (pre-vista)
> > and older versions of the JVM, the NIO libraries do not support IPv6
> > (see bug report).
> >
> > As a side note, the poster could switch from NIO to the APR connector,
> > and it would likely resolve his problem (just like he reported
> > switching to the BIO connector resolved his problem). Just assuming
> > that the poster wants to stick with the NIO connector.
> >
> > Dan
> >
>
> Yes, Dan. But the OP stated he is using Windows Server 2008, which is the
> server version of "Vista". Since he doesn't say he's on 2008 R2 (which is
> Windows 7 Server), so we'll assume that he's at least at a Vista-level
> networking.
>
> The bug you mention is specifically about dual-mode socket support, that
> is, being able to specify the port and not the address and having Java set
> up to sockets which listen/talk on both the IPv4 & IPv6 addresses of the
> machine. At least if I read it correctly. Re-reading it, it might not be
> there for NIO, no matter what you try. My work-around would specifically
> show whether the support is there or not for IPv6 in NIO, i.e., use it as a
> diagnostic tool, if nothing else.
>
> But yes, reading the bug, really closely, makes it appear that the support
> for NIO IPv6 was not back-ported to JDK6 until this last July, specifically
> 6u33-b34. So the OP should probably start up upgrading his Java to
> jdk1.6_34 or later and see if that doesn't fix it first.
>
> Personally, I prefer the APR to NIO, but mainly because SSL is easier to
> manage under APR. I believe there are some esoteric advantages to using
> NIO, but I'd have to go back to the comparison chart to tell you what they
> are. The OP may have a specific use case that requires those features.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: HTTP NIO connector not supporting IPv6
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Daniel Mikusa [mailto:dmikusa@vmware.com]
> Sent: Wednesday, September 12, 2012 2:14 PM
> To: Tomcat Users List
> Subject: Re: HTTP NIO connector not supporting IPv6
>
> On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
>
> >> -----Original Message-----
> >> From: Daniel Mikusa [mailto:dmikusa@vmware.com]
> >> Sent: Wednesday, September 12, 2012 10:00 AM
> >> To: Tomcat Users List
> >> Subject: Re: HTTP NIO connector not supporting IPv6
> >>
> >> On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
> >>
> >>> 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"/>
> >>>
> >>
> >> Tried it on my MBP (10.7 w/Java 1.6.0_35) and it worked fine. Tried
> >> on Windows XP (only version I have available) w/ Java 1.6.0_35 and
> >> was able to replicate the problem behavior. According to the
> >> following bug report this is a limitation of the OS / JVM. Looks
> >> like a recent versions of Windows and a recent version of the JVM
> are
> >> required to resolve this.
> >>
> >> Try upgrading from 1.6.0_25 to 1.6.0_35.
> >>
> >> http://bugs.sun.com/view_bug.do?bug_id=6230761
> >>
> >> Dan
> >>
> > One workaround is to explicitly define the IPv4 and IPv6 addressing
> in the <connector>.
> > That is, add address="0.0.0.0" for any IPv4 connectors and
> > address="[::]" for any IPv6 connectors. (Or use your real addresses
> instead of the "any" addresses listed here.) This means setting up 2
> sets of connectors for each port/protocol, but there's nothing wrong
> with being explicit.
> > This is what I had to do to get the APR protocol to set up for IPv4.
>
>
> With all due respect, I do not think that this is going to work for the
> poster. You're saying that your workaround was for an issue with the
> APR connector, but the poster is using the NIO connector. The APR
> connector does not use NIO or the JVM, so I don't think your workaround
> is relevant. In fact I tried your workaround previously without
> success. The problem is that on older versions of Windows (pre-vista)
> and older versions of the JVM, the NIO libraries do not support IPv6
> (see bug report).
>
> As a side note, the poster could switch from NIO to the APR connector,
> and it would likely resolve his problem (just like he reported
> switching to the BIO connector resolved his problem). Just assuming
> that the poster wants to stick with the NIO connector.
>
> Dan
>
Yes, Dan. But the OP stated he is using Windows Server 2008, which is the server version of "Vista". Since he doesn't say he's on 2008 R2 (which is Windows 7 Server), so we'll assume that he's at least at a Vista-level networking.
The bug you mention is specifically about dual-mode socket support, that is, being able to specify the port and not the address and having Java set up to sockets which listen/talk on both the IPv4 & IPv6 addresses of the machine. At least if I read it correctly. Re-reading it, it might not be there for NIO, no matter what you try. My work-around would specifically show whether the support is there or not for IPv6 in NIO, i.e., use it as a diagnostic tool, if nothing else.
But yes, reading the bug, really closely, makes it appear that the support for NIO IPv6 was not back-ported to JDK6 until this last July, specifically 6u33-b34. So the OP should probably start up upgrading his Java to jdk1.6_34 or later and see if that doesn't fix it first.
Personally, I prefer the APR to NIO, but mainly because SSL is easier to manage under APR. I believe there are some esoteric advantages to using NIO, but I'd have to go back to the comparison chart to tell you what they are. The OP may have a specific use case that requires those features.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: HTTP NIO connector not supporting IPv6
Posted by Daniel Mikusa <dm...@vmware.com>.
On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
>> -----Original Message-----
>> From: Daniel Mikusa [mailto:dmikusa@vmware.com]
>> Sent: Wednesday, September 12, 2012 10:00 AM
>> To: Tomcat Users List
>> Subject: Re: HTTP NIO connector not supporting IPv6
>>
>> On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
>>
>>> 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"/>
>>>
>>
>> Tried it on my MBP (10.7 w/Java 1.6.0_35) and it worked fine. Tried on
>> Windows XP (only version I have available) w/ Java 1.6.0_35 and was
>> able to replicate the problem behavior. According to the following bug
>> report this is a limitation of the OS / JVM. Looks like a recent
>> versions of Windows and a recent version of the JVM are required to
>> resolve this.
>>
>> Try upgrading from 1.6.0_25 to 1.6.0_35.
>>
>> http://bugs.sun.com/view_bug.do?bug_id=6230761
>>
>> Dan
>>
> One workaround is to explicitly define the IPv4 and IPv6 addressing in the <connector>.
> That is, add address="0.0.0.0" for any IPv4 connectors and address="[::]" for any IPv6 connectors. (Or use your real addresses instead of the "any" addresses listed here.)
> This means setting up 2 sets of connectors for each port/protocol, but there's nothing wrong with being explicit.
> This is what I had to do to get the APR protocol to set up for IPv4.
With all due respect, I do not think that this is going to work for the poster. You're saying that your workaround was for an issue with the APR connector, but the poster is using the NIO connector. The APR connector does not use NIO or the JVM, so I don't think your workaround is relevant. In fact I tried your workaround previously without success. The problem is that on older versions of Windows (pre-vista) and older versions of the JVM, the NIO libraries do not support IPv6 (see bug report).
As a side note, the poster could switch from NIO to the APR connector, and it would likely resolve his problem (just like he reported switching to the BIO connector resolved his problem). Just assuming that the poster wants to stick with the NIO connector.
Dan
>
> Plus, why do you have asterisks (*) bracketing the protocols? All examples I've ever seen don't use them. They are just quoted strings. From the default server.xml shipped with Tomcat:
> <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
> maxThreads="150" scheme="https" secure="true"
> clientAuth="false" sslProtocol="TLS" />
>
>
>
> ---------------------------------------------------------------------
> 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
RE: HTTP NIO connector not supporting IPv6
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----Original Message-----
> From: Daniel Mikusa [mailto:dmikusa@vmware.com]
> Sent: Wednesday, September 12, 2012 10:00 AM
> To: Tomcat Users List
> Subject: Re: HTTP NIO connector not supporting IPv6
>
> On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
>
> > 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"/>
> >
>
> Tried it on my MBP (10.7 w/Java 1.6.0_35) and it worked fine. Tried on
> Windows XP (only version I have available) w/ Java 1.6.0_35 and was
> able to replicate the problem behavior. According to the following bug
> report this is a limitation of the OS / JVM. Looks like a recent
> versions of Windows and a recent version of the JVM are required to
> resolve this.
>
> Try upgrading from 1.6.0_25 to 1.6.0_35.
>
> http://bugs.sun.com/view_bug.do?bug_id=6230761
>
> Dan
>
One workaround is to explicitly define the IPv4 and IPv6 addressing in the <connector>.
That is, add address="0.0.0.0" for any IPv4 connectors and address="[::]" for any IPv6 connectors. (Or use your real addresses instead of the "any" addresses listed here.)
This means setting up 2 sets of connectors for each port/protocol, but there's nothing wrong with being explicit.
This is what I had to do to get the APR protocol to set up for IPv4.
Plus, why do you have asterisks (*) bracketing the protocols? All examples I've ever seen don't use them. They are just quoted strings. From the default server.xml shipped with Tomcat:
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: HTTP NIO connector not supporting IPv6
Posted by Daniel Mikusa <dm...@vmware.com>.
On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
> 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"/>
>
Tried it on my MBP (10.7 w/Java 1.6.0_35) and it worked fine. Tried on Windows XP (only version I have available) w/ Java 1.6.0_35 and was able to replicate the problem behavior. According to the following bug report this is a limitation of the OS / JVM. Looks like a recent versions of Windows and a recent version of the JVM are required to resolve this.
Try upgrading from 1.6.0_25 to 1.6.0_35.
http://bugs.sun.com/view_bug.do?bug_id=6230761
Dan
>
>
>
>
>
>
> 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
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: HTTP NIO connector not supporting IPv6
Posted by Aditi Sinha <ad...@gmail.com>.
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
>
>
RE: HTTP NIO connector not supporting IPv6
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
> -----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
RE: HTTP NIO connector not supporting IPv6
Posted by Jeffrey Janner <Je...@PolyDyne.com>.
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
> -----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