Ubuntu 22.04.3
Thanks. Output is indeed "0". So it listens to both protocol versions. Will
stick with this of course :)
--
Christoph
> Am 08.01.2024 um 11:15 schrieb EML :
>
> Run this command (I'm assuming you're on Linux):
>
> $ cat /proc/sys/net/ipv6/bi
Run this command (I'm assuming you're on Linux):
$ cat /proc/sys/net/ipv6/bindv6only
The default output is 0 on Linux (the Windows equivalent is apparently
1). 0 means that an IPv6 socket will connect to *both* IPv6 and IPv4
(look up IPV6_V6ONLY).
You can force Java to listen to
ain] org.apache.coyote.AbstractProtocol.start
Starting ProtocolHandler ["https-openssl-apr-8443"]
08-Jan-2024 10:26:23.133 INFO [main] org.apache.catalina.startup.Catalina.start
Server startup in [27735] milliseconds
root@mail:/var/lib/tomcat9/logs# lsof -i :8443
COMMANDPID USER FD
> which address will be used for listening on the specified port. By
> default, the connector will listen all local addresses. Unless the JVM
> is configured otherwise using system properties, the Java based
> connectors (NIO, NIO2) will listen on both IPv4 and IPv6 addresses when
> conf
O2) will listen on both IPv4 and IPv6 addresses when
configured with either 0.0.0.0 or ::. The APR/native connector will only
listen on IPv4 addresses if configured with 0.0.0.0 and will listen on
IPv6 addresses (and optionally IPv4 addresses depending on the setting
of ipv6v6only) if configured
On 11/28/23 05:24, Christoph Kukulies wrote:
root@mail:/var/lib/tomcat9/logs# lsof -i :8080
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 58986 tomcat 37u IPv6 571175 0t0 TCP *:http-alt (LISTEN)
root@mail:/var/lib/tomcat9/logs#
On my local desktop (running Ubuntu
tartup.VersionLoggerListener.log Command line
>>>> argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
>>>> 28-Nov-2023 13:15:43.762 INFO [main]
>>>> org.apache.catalina.startup.VersionLoggerListener.log Command line
>>>> argument:
].
28-Nov-2023 13:15:43.769 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
capabilities: IPv6 [true], sendfile [true], accept filters [false],
random
[true], UDS [true].
28-Nov-2023 13:15:43.771 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL
configuration: useAprConne
at9
>> 28-Nov-2023 13:15:43.762 INFO [main]
>> org.apache.catalina.startup.VersionLoggerListener.log Command line
>> argument: -Dcatalina.home=/usr/share/tomcat9
>> 28-Nov-2023 13:15:43.763 INFO [main]
>> org.apache.catalina.startup.VersionLoggerListener.log Command line
>> argument: -Djava.io.tmpdir=/tmp
>> 28-No
rListener.log Command line
> argument: -Dcatalina.home=/usr/share/tomcat9
> 28-Nov-2023 13:15:43.763 INFO [main]
> org.apache.catalina.startup.VersionLoggerListener.log Command line
> argument: -Djava.io.tmpdir=/tmp
> 28-Nov-2023 13:15:43.768 INFO [main]
> org.apache.catalina.core.AprLifecycleListener.
1.7.0].
28-Nov-2023 13:15:43.769 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities:
IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true].
28-Nov-2023 13:15:43.771 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycl
Thanks for all the responses.
Regards,
Nitish
On Wed, Aug 3, 2022 at 2:58 PM Konstantin Kolinko
wrote:
> ср, 3 авг. 2022 г. в 10:19, Nitish Chitta :
> >
> > Hello Team,
> > I wanted to know if Tomcat 7 supports requests with IPv6 addresses in the
> > URL as I am get
ср, 3 авг. 2022 г. в 10:19, Nitish Chitta :
>
> Hello Team,
> I wanted to know if Tomcat 7 supports requests with IPv6 addresses in the
> URL as I am getting an HTTP 404 error when trying to hit the server with an
> IPv6 address.
1. Tomcat 7 has reached End of Life and is no longe
check if tomcat is listening on ipv6, using ss or netstat command.
need more details about your environment, how requests are pass to
container, etc...
On Wed, Aug 3, 2022 at 3:26 PM Nitish Chitta wrote:
>
> I have done the required changes i.e added the IPv6 address to the
> connector
> 2022年8月3日 15:18，Nitish Chitta 写道：
>
> Hello Team,
> I wanted to know if Tomcat 7 supports requests with IPv6 addresses in the
> URL as I am getting an HTTP 404 error when trying to hit the server with an
> IPv6 address.
Don’t you get a 404 error when you use an IPV4 add
I have done the required changes i.e added the IPv6 address to the
connector that the server should listen on. Do I have to add any other
property or am I missing something?
On Wed, Aug 3, 2022 at 12:51 PM Jason Wee wrote:
> yes, it should, read here
> https://tomcat.apache.org/tomcat-7
yes, it should, read here
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html
On Wed, Aug 3, 2022 at 3:19 PM Nitish Chitta wrote:
>
> Hello Team,
> I wanted to know if Tomcat 7 supports requests with IPv6 addresses in the
> URL as I am getting an HTTP 404 error when tryin
Hello Team,
I wanted to know if Tomcat 7 supports requests with IPv6 addresses in the
URL as I am getting an HTTP 404 error when trying to hit the server with an
IPv6 address.
Thanks & Regards,
Nitish
Nevermind. For some reason we had omitted this is already supported by the
ipv6Canonical flag.
RTFM!
Manuel Dominguez Sarmiento
> On 13 Apr 2020, at 20:46, Manuel Dominguez Sarmiento wrote:
>
> Hi, we are in the middle of a thorough review to fully support IPv6 across
> our
Am 2020-04-14 um 01:45 schrieb Manuel Dominguez Sarmiento:
Hi, we are in the middle of a thorough review to fully support IPv6
across our platform. It has come to our attention that Java does not
fully conform to RFC 5952 section 4 which deals with IPv6 zero
compression (i.e. ::1 instead of 0
Hi, we are in the middle of a thorough review to fully support IPv6
across our platform. It has come to our attention that Java does not
fully conform to RFC 5952 section 4 which deals with IPv6 zero
compression (i.e. ::1 instead of 0:0:0:0:0:0:0:1 for localhost). We have
confirmed that
Hi,
On Tue, Mar 17, 2020 at 9:22 PM
wrote:
> We have a team having issues with Tomcat, AJP, and switching to IPv6. They
> are currently running version 9.0.31. Below are the errors being received:
>
> [Tue Mar 17 10:50:38 2020] [1412:139846332929792] [error]
> ajp_service::jk_ajp
We have a team having issues with Tomcat, AJP, and switching to IPv6. They are
currently running version 9.0.31. Below are the errors being received:
[Tue Mar 17 10:50:38 2020] [1412:139846332929792] [error]
ajp_service::jk_ajp_common.c (2796): (Greenworker1) connecting to tomcat failed
(rc=-3
On 10.03.2020 15:44, Martin Grigorov wrote:
On Tue, Mar 10, 2020 at 3:56 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 3/10/20 04:43, Martin Grigorov wrote:
We can define custom address like "loopback" for which Tomca
On 11.03.2020 09:30, Piyush Kumar Nayak wrote:
What's the point of " ipv6v6only" attribute. The doc says :
"If listening on an IPv6 address on a dual stack system, should the connector only
listen on the IPv6 address? If not specified the default is false and the connector
What's the point of " ipv6v6only" attribute. The doc says :
"If listening on an IPv6 address on a dual stack system, should the connector
only listen on the IPv6 address? If not specified the default is false and the
connector will listen on the IPv6 address and the equiva
On Tue, Mar 10, 2020 at 3:56 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Martin,
>
> On 3/10/20 04:43, Martin Grigorov wrote:
> > We can define custom address like "loopback" for which Tomcat will
> > bind on both "127.0.0.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 3/10/20 04:43, Martin Grigorov wrote:
> We can define custom address like "loopback" for which Tomcat will
> bind on both "127.0.0.1" and "::1" depending on the values of
> java.net.preferIPv4Stack and java.net.preferIPv6Addresses, but I
Hi,
On Mon, Mar 9, 2020 at 9:34 PM Piyush Kumar Nayak
wrote:
> There appears to be a change in the behavior of AJP connector in Tomcat,
> with respect to the protocol stack of the loopback address it binds to.
> With older versions it binds to both IPv6 and IPv4 interface, but with
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Piyush,
On 3/9/20 15:34, Piyush Kumar Nayak wrote:
> There appears to be a change in the behavior of AJP connector in
Tomcat, with respect to the protocol stack of the loopback address it
binds to.
> With older versions it binds to both IP
There appears to be a change in the behavior of AJP connector in Tomcat, with
respect to the protocol stack of the loopback address it binds to.
With older versions it binds to both IPv6 and IPv4 interface, but with 9.0.31
it appears to bind to IPv4 only, if the address attribute is removed from
Chris,
In both the cases, ISAPI and mod_jk, the hostname is set to "localhost"
Tomcat and webserver are on the same host machine.
-Original Message-
From: Christopher Schultz
Sent: Friday, March 6, 2020 8:20 PM
To: users@tomcat.apache.org
Subject: Re: bind Tomcat to IPv
-chris
> -Original Message- From: Mark H. Wood
> Sent: Thursday, March 5, 2020 10:28 PM To: users@tomcat.apache.org
> Subject: Re: bind Tomcat to IPv4 and IPv6 loopback, Tomcat 9.0.31
>
> On Thu, Mar 05, 2020 at 01:52:57PM +, Piyush Kumar Nayak
> wrote:
>> Is there a way to
Thanks Mark,
Two connector configs works.
Any ideas, on why the behavior if different for ISAPI and mod_jk modules?
-Original Message-
From: Mark H. Wood
Sent: Thursday, March 5, 2020 10:28 PM
To: users@tomcat.apache.org
Subject: Re: bind Tomcat to IPv4 and IPv6 loopback, Tomcat 9.0.31
On Thu, Mar 05, 2020 at 01:52:57PM +, Piyush Kumar Nayak wrote:
> Is there a way to get Tomcat's AJP connector to bind to both IPv4 and IPv6
> loopback addresses.
>
> By default, it seems that Tomcat binds to IPv4 loopback
> Default connector config :
> packetS
Hi,
Check this thread:
https://lists.apache.org/thread.html/r1f83f0c731a8737fdf4dad13ae402acd2fdc1ab1a86605af5b496a5f%40%3Cusers.tomcat.apache.org%3E
On Thu, Mar 5, 2020 at 3:53 PM Piyush Kumar Nayak
wrote:
>
> Is there a way to get Tomcat's AJP connector to bind to both IP
Is there a way to get Tomcat's AJP connector to bind to both IPv4 and IPv6
loopback addresses.
By default, it seems that Tomcat binds to IPv4 loopback
Default connector config :
netstat -ano | findstr 8014
TCP 127.0.0.1:8014 0.0.0.0:0 LISTENING 8616
TCP 127.0.0.1:8014 127.0.0.1:
On Mon, Mar 5, 2018 at 10:35 AM, Mark Thomas wrote:
> On 05/03/18 15:00, Mark Thomas wrote:
>> On 05/03/18 02:02, Rick Trudeau wrote:
>>> Hi,
>>> I'm having some problems using SSL on my connector when binding it to
>>> a specific IPv6 address.
>>>
On 05/03/18 15:00, Mark Thomas wrote:
> On 05/03/18 02:02, Rick Trudeau wrote:
>> Hi,
>> I'm having some problems using SSL on my connector when binding it to
>> a specific IPv6 address.
>> I'm trying this on Tomcat v 8.5.28, Ubuntu 14.04, JVM v1.8.0_161-b12.
On 05/03/18 02:02, Rick Trudeau wrote:
> Hi,
> I'm having some problems using SSL on my connector when binding it to
> a specific IPv6 address.
> I'm trying this on Tomcat v 8.5.28, Ubuntu 14.04, JVM v1.8.0_161-b12.
>
> My connector config looks like this:
>
Hi,
I'm having some problems using SSL on my connector when binding it to
a specific IPv6 address.
I'm trying this on Tomcat v 8.5.28, Ubuntu 14.04, JVM v1.8.0_161-b12.
My connector config looks like this:
catalina.out shows this exception immediately after startup. I think
it indic
Hello
I am having below query for tomcat 8.5.15 version. Please help.
I am using tomcat 8.5.15 and my network is supporting both ipv4 and ipv6
address stacks. However, I want tomcat to listen to only ipv6 address (not
ipv4).
I was trying to find the solution on google and reached to tomcat&#
59018 :::*LISTEN
> tcp6 0 0 :::587 :::*LISTEN
> tcp6 0 0 :::57999 :::*LISTEN
> tcp6 0 0 :::143 :::*LISTEN
> tcp6 0 0 :::111 :::*LISTEN
> tcp6
did a
service tomcat7 restart
netstat -an | grep 8080
and saw tcp6 still listed and no tcp
Now it look like this: (after enabling ipv6 in sysctl.conf again):
tcp0 0 127.0.0.1:49393 127.0.0.1:8009 ESTABLISHED
tcp0 0 127.0.0.1:49395 127.0.0.1:8009
address="0.0.0.0" redirectPort="8443" />
>
> I then did a
> service tomcat7 restart
> netstat -an | grep 8080
>
>
> and saw tcp6 still listed and no tcp
>
> Now it look like this: (after enabling ipv6 in sysctl.conf again):
>
> tcp0
Hi Chris,
it is (was) in server.xml: (I now only have tomcat listening on port
8009 proxy_ajp)
I then did a
service tomcat7 restart
netstat -an | grep 8080
and saw tcp6 still listed and no tcp
Now it look like this: (after enabling ipv6 in sysctl.conf again):
tcp0 0
stening
>>> to
>>>
>>> tcp6 00 :::8080 :::* LISTEN
>>>
>>> How can I turn that to
>>>
>>> tcp 0 0 0.0.0.0:80800.0.0.0:* LISTEN
>>>
>>>
>>> Do I
to
tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN
Do I have to disable ipv6 in Ubuntu first or can I switch that by
tweaking some config file or so?
Try setting the address attribute of the connector to "0.0.0.0"
Mark
You mean in server.xml: in the section addres
;
> tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN
>
>
> Do I have to disable ipv6 in Ubuntu first or can I switch that by
> tweaking some config file or so?
Try setting the address attribute of the connector to "0.0.0.0"
Mark
---
I installed tomcat7 (apt-get) on an Ubuntu 14.04.3 LTS machine and found
it being installed as listening
to
tcp6 00 :::8080 :::* LISTEN
How can I turn that to
tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN
Do I have to disable ipv6 in
In web browser Firefox, I set Hostname property to IPv6
> > address(2001:c0a8::1) using JK Status Manager, But error occured.
> >
> > Is there a solution to the problem?
> >
> > -mod_jk.log
> > [Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [info]
>
2014-06-12 13:34 GMT+04:00 Hiroto Shimizu :
> Hi
>
> I use mod_jk 1.2.40, httpd-2.2.15-29.el6.centos.x86_64.
> In web browser Firefox, I set Hostname property to IPv6
> address(2001:c0a8::1) using JK Status Manager, But error occured.
>
> Is there a solution to the problem?
&
Hi
I use mod_jk 1.2.40, httpd-2.2.15-29.el6.centos.x86_64.
In web browser Firefox, I set Hostname property to IPv6
address(2001:c0a8::1) using JK Status Manager, But error occured.
Is there a solution to the problem?
-mod_jk.log
[Thu Jun 12 11:09:13.029 2014] [4233:140197382711040] [info
re Tomcat in ipv6 ?
>
> What are the corresponding changes to be done in server.xml ?
>
> Is there a specific JVM argument ?
>
> Thanks in advance. Best regards Olivier.
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools - http://gpgtools
Hello to all,
How to configure Tomcat in ipv6 ?
What are the corresponding changes to be done in server.xml ?
Is there a specific JVM argument ?
Thanks in advance.
Best regards Olivier.
> -Original Message-
> From: olivier giorgi [mailto:olivier_gio...@yahoo.fr]
> Sent: Thursday, August 01, 2013 11:17 AM
> To: users@tomcat.apache.org
> Subject: Do you know how to configure Tomcat in ipv6 ?
>
> Hello to all,
>
> Please, could you help me
To: users@tomcat.apache.org
Subject: Do you know how to configure Tomcat in ipv6 ?
Hello to all,
Please, could you help me about the following subject:
How to configure Tomcat in ipv6 ?
Thanks in advance.
Best regards Olivier
Hello to all,
Please, could you help me about the following subject:
How to configure Tomcat in ipv6 ?
Thanks in advance.
Best regards Olivier.
Well, you could search the archives... that's what they are there for.
Or, you could read the online documentation:
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard_Implementation
Look at the "address" attribute. On many systems, a single interface
has both IPv4 and IPv
gt; > I have a web application hosted on Apache Tomcat Version 7.0.035.
> > We are trying to make the web application run IPv6 environment.
> >
> > Environment Details
> > Windows 2008 server machine, 64-bit OS
> > Java version: JRE 1.7.x
> >
> > The home pag
2013/3/28 Geett Chanddra Singha :
> Hi All,
>
> I have a web application hosted on Apache Tomcat Version 7.0.035.
> We are trying to make the web application run IPv6 environment.
>
> Environment Details
> Windows 2008 server machine, 64-bit OS
> Java version: JRE 1.7.x
Hi All,
I have a web application hosted on Apache Tomcat Version 7.0.035.
We are trying to make the web application run IPv6 environment.
Environment Details
Windows 2008 server machine, 64-bit OS
Java version: JRE 1.7.x
The home page of web application is not accessible using the IPv6 address
>
>
> On 6.3.2013 15:14, Geett Chanddra Singha wrote:
>
>> Right? What about IPv4? Do you use it? Is it similar situation when you
>> use
>> IPv4 (works only when you add "protocol" attribute)? Are you sure that
>> IPv6
>> protocol is being us
Geett,
On 6.3.2013 15:14, Geett Chanddra Singha wrote:
Right? What about IPv4? Do you use it? Is it similar situation when you use
IPv4 (works only when you add "protocol" attribute)? Are you sure that IPv6
protocol is being used? Do you access your server using hostname or
Thanks Ognjen!
1. Did I understand correctly:
- You are able to access your Tomcat server using HTTPS over IPv6.
- If you do not add "protocol" attribute to your HTTP connector, you are
unable to access Tomcat server using HTTP.
- After you add "protocol" attribute everythi
to access your Tomcat server using HTTPS over IPv6.
- If you do not add "protocol" attribute to your HTTP connector, you are
unable to access Tomcat server using HTTP.
- After you add "protocol" attribute everything works as expected.
Right? What about IPv4? Do you u
Hi,
- what version of Tomcat (x.y.z) you are using
- *Tomcat Version 6.0.035*
- under what version of Java
- *Java version 1.6.033*
*
*
- under what platform O.S.
- *Windows and Linux*
Regards,
Geett
On Wed, Mar 6, 2013 at 3:56 PM, André Warnier wrote:
> Geett Chanddra Singha wrote:
>
>>
Geett Chanddra Singha wrote:
Hi All,
I would like to know is that is it ok to add this as shown below
protocol="org.apache.coyote.http11.Http11Protocol"
in
As there are certainly differences in the attributes between different versions of
Tomcat, it would be a good idea to mention
- wh
Chris,
Thanks for letting me know,
What I wanted to know is that is it ok to add this as shown below
protocol="org.apache.coyote.http11.Http11Protocol"
in
Regards::Geet
On Wed, Mar 6, 2013 at 11:36 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Geett,
On 3/5/13 10:45 PM, Geett Chanddra Singha wrote:
> Hi All,
>
> I am using Apache Tomcat version 6.0.035 for a web application,
> everything seems to be working fine when I access the application
> in HTTPS mode,however if I try to access in
wrote:
I have now this in my server.xml: For IPv4: For IPv6:
With this setup I can connect to port 80 over Ipv4 And IPv6 to
my Linux box.
So, a recap:
* NIO/BIO connector binds to both IPv4 and IPv6 when no "address"
is specified
* APR connector binds only to IPv6 interface is IPv6 is
now this in my server.xml: For IPv4: For IPv6:
With this setup I can connect to port 80 over Ipv4 And IPv6 to
my Linux box.
So, a recap:
* NIO/BIO connector binds to both IPv4 and IPv6 when no "address"
is specified
* APR connector binds only to IPv6 interface is IPv6 is
available,
I have now this in my server.xml: For IPv4: >> port="80" protocol="HTTP/1.1" connectionTimeout="2"
>>> redirectPort="8443" address="0.0.0.0" /> For IPv6: >> port="80" protocol="HTTP/1.1" connectionTimeo
Zorro wrote:
Op 27-11-2012 20:00, Christopher Schultz schreef:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm-Jan,
On 11/26/12 3:16 PM, Zorro wrote:
I have now this in my server.xml: For IPv4: For IPv6:
With this setup I can connect to port 80 over Ipv4 And IPv6 to my
Linux box.
So
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Tuesday, November 27, 2012 1:01 PM
> To: Tomcat Users List
> Subject: Re: Using the Tomcat Native Library can only connect over ipv6
> But not over ipv4
>
> -
Op 27-11-2012 20:00, Christopher Schultz schreef:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm-Jan,
On 11/26/12 3:16 PM, Zorro wrote:
I have now this in my server.xml: For IPv4: For IPv6:
With this setup I can connect to port 80 over Ipv4 And IPv6 to my
Linux box.
So, a recap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harm-Jan,
On 11/26/12 3:16 PM, Zorro wrote:
> I have now this in my server.xml: For IPv4: protocol="HTTP/1.1" connectionTimeout="2" redirectPort="8443"
> address="0.0.0.0" /> For IPv6: protocol=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 11/26/12 3:14 PM, André Warnier wrote:
> Also, I don't know if this is really relevant here, but I seem to
> remember a parameter or attribute somewhere named
> "preferIPv4Stack"/"preferIPv6Stack".
That is for configuring the Java network
Op 26-11-2012 20:31, Jeffrey Janner schreef:
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, November 26, 2012 1:17 PM
To: Tomcat Users List
Subject: Re: Using the Tomcat Native Library can only connect over ipv6
But not over ipv4
Jeffrey Janner wrote:
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, November 26, 2012 1:17 PM
To: Tomcat Users List
Subject: Re: Using the Tomcat Native Library can only connect over ipv6
But not over ipv4
-BEGIN PGP SIGNED MESSAGE
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Monday, November 26, 2012 1:17 PM
> To: Tomcat Users List
> Subject: Re: Using the Tomcat Native Library can only connect over ipv6
> But not over ipv4
>
> -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zorro,
On 11/23/12 4:37 PM, Zorro wrote:
> its not really a problem but if we ever migrate the internet to
> IPv6 it would be brilliant to have the connector serving both
> protocols which the http-bio-80 connector seems to be able to d
1 80 I can connect to Tomcat!
Using the http-bio-80 connector I can connect to Tomcat over ipv4
as well over ipv6. Both telnet 127.0.0.1 80 and telnet ::1 80 do
connect to Tomcat.
Is there a way to use the Apache Tomcat Native Library also for
ipv4 connections?
Try setting address="127.0.0.
ttp-bio-80 connector I can connect to Tomcat over ipv4
as well over ipv6. Both telnet 127.0.0.1 80 and telnet ::1 80 do
connect to Tomcat.
Is there a way to use the Apache Tomcat Native Library also for
ipv4 connections?
Try setting address="127.0.0.1" in your . Or "0.0.0.0" if
ctor I can connect to Tomcat over ipv4
as well over ipv6. Both telnet 127.0.0.1 80 and telnet ::1 80 do
connect to Tomcat.
Is there a way to use the Apache Tomcat Native Library also for
ipv4 connections?
Try setting address="127.0.0.1" in your . Or "0.0.0.0" if
you want to
cannot connect over ipv4.
Using Tomcat with the Native Library on Fedora 14 everything starts
up fine. However a telnet 127.0.0.1 80 gives a 'Connection
refused'. But with a telnet ::1 80 I can connect to Tomcat!
Using the http-bio-80 connector I can connect to Tomcat over ipv4
as well
over ipv4.
Using Tomcat with the Native Library on Fedora 14 everything starts
up fine. However a telnet 127.0.0.1 80 gives a 'Connection
refused'. But with a telnet ::1 80 I can connect to Tomcat!
Using the http-bio-80 connector I can connect to Tomcat over ipv4
as well over ipv6. B
omcat with the Native Library on Fedora 14 everything starts
> up fine. However a telnet 127.0.0.1 80 gives a 'Connection
> refused'. But with a telnet ::1 80 I can connect to Tomcat!
>
> Using the http-bio-80 connector I can connect to Tomcat over ipv4
> as well over ipv6.
ction refused'.
But with a telnet ::1 80 I can connect to Tomcat!
Using the http-bio-80 connector I can connect to Tomcat over ipv4 as
well over ipv6.
Both telnet 127.0.0.1 80 and telnet ::1 80 do connect to Tomcat.
Is there a way to use the Apache Tomcat Native Library also for ipv4
c
usa [mailto:dmik...@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 Me
> -Original Message-
> From: Daniel Mikusa [mailto:dmik...@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:
>
&g
On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
>> -Original Message-
>> From: Daniel Mikusa [mailto:dmik...@vmware.com]
>> Sent: Wednesday, September 12, 2012 10:00 AM
>> To: Tomcat Users List
>> Subject: Re: HTTP NIO connector not supporting IPv6
>
> -Original Message-
> From: Daniel Mikusa [mailto:dmik...@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:
&g
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.
>
>
> redirectPort="
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.
Below configuration supports IPv6. The only difference is the protocol.
Please let me know if
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@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 I
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
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
&
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(d
nha wrote:
> > Wanted to know if the HTTP NIO connectors do not support IPv6?
>
> AFAIK, all Tomcat connectors support IPv6 if your JVM and OS support
> IPv6 (and tcnative/apr support IPv6 if you are using APR). If you are
> having a specific problem, please start another thread
1 - 100 of 218 matches
Mail list logo
