On 27/05/2021 13:24, Mark Thomas wrote:
On 27/05/2021 11:12, Michael Osipov wrote:
Am 2021-05-27 um 11:52 schrieb Mark Thomas:
Michael,
I think we need to step back a bit.
I am unable to recreate the issue you describe. I am using:
- Windows Server 2019
- IPv6 enabled (and IPv4 and both have addresses)
- Apache Tomcat 9.0.46
- Apache Tomcat Native 1.2.28
- AprLifecycleListener is enabled
- No address configured for Connector
- Logs confirm http-apr-8080
I can access the default home page via both IPv4 and IPv6 from both
the local machine and remotely.
<snip/>
Please try my simple program from this gist:
https://gist.github.com/michael-o/dfb86df472f62d2b2dff6ef12ee3758e
<snip/>
Does this help?
Thanks. That helped me narrow down where the differences where. If you
run Tomcat as a service it binds both 0.0.0.0:8080 and [::]:8080. If you
run it from the command line, it only binds [::]:8080.
I'll take a look at the proposed APR patch next.
I can confirm that the patch to APR fixes the issue for me too.
With the original 1.2.28 DLL, starting Tomcat on the command line only
binds to IPv6.
With a patched 1.2.29-dev DLL, starting Tomcat on the command line binds
to IPv6 and IPv4.
I'll tag and start the release process for Tomcat Native shortly.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
