You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Graham Leggett <mi...@sharp.fm.INVALID> on 2023/03/06 23:01:14 UTC
tomcat-native v2.0+ breaks unix domain socket support on java16-
Hi all,
A while back I added unix domain socket support to tomcat-native, and patched tomcat to use it until java16 is available.
Unfortunately unix domain socket support was removed from tomcat-native 2.0+, and now tomcat-native 2.0+ is appearing in distros, meaning that unix domain socket support just broke.
https://tomcat.apache.org/native-doc/miscellaneous/changelog.html
"Remove all API methods (and supporting code) that are not used by Tomcat 10.1.x to support the use of OpenSSL as a replacement for JSSE to provide TLS functionality. (markt)”
Is there a way to fix this, or has tomcat just broken everything for anyone in a RHEL environment?
Regards,
Graham
—
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: tomcat-native v2.0+ breaks unix domain socket support on java16-
Posted by Konstantin Kolinko <kn...@gmail.com>.
вт, 7 мар. 2023 г. в 02:01, Graham Leggett <mi...@sharp.fm.invalid>:
>
> Hi all,
>
> A while back I added unix domain socket support to tomcat-native, and patched tomcat to use it until java16 is available.
Java 17 (LTS) is already available for a while.
Is it available for your platform?
> Unfortunately unix domain socket support was removed from tomcat-native 2.0+, and now tomcat-native 2.0+ is appearing in distros, meaning that unix domain socket support just broke.
>
> https://tomcat.apache.org/native-doc/miscellaneous/changelog.html
>
> "Remove all API methods (and supporting code) that are not used by Tomcat 10.1.x to support the use of OpenSSL as a replacement for JSSE to provide TLS functionality. (markt)”
>
> Is there a way to fix this, or has tomcat just broken everything for anyone in a RHEL environment?
Tomcat 9.0 and 8.5 are expected to run with Tomcat Native 1.2.x and
that version is still supported.
(They can run with Tomcat Native 2.0.x as long as APR connector is not used).
Tomcat Native 2.0 is the version used by Tomcat 10.1.x and beyond.
Tomcat 10.1.x does not have the APR connector. It has only NIO and
NIO2. The APR connector has been removed.
Is your Tomcat failing to start because it is explicitly configured to
use the APR connector (Http11AprProtocol, AjpAprProtocol)?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: tomcat-native v2.0+ breaks unix domain socket support on java16-
Posted by Mark Thomas <ma...@apache.org>.
On 07/03/2023 07:45, Rémy Maucherat wrote:
> On Tue, Mar 7, 2023 at 12:01 AM Graham Leggett <mi...@sharp.fm.invalid> wrote:
>>
>> Hi all,
>>
>> A while back I added unix domain socket support to tomcat-native, and patched tomcat to use it until java16 is available.
>>
>> Unfortunately unix domain socket support was removed from tomcat-native 2.0+, and now tomcat-native 2.0+ is appearing in distros, meaning that unix domain socket support just broke.
>>
>> https://tomcat.apache.org/native-doc/miscellaneous/changelog.html
>>
>> "Remove all API methods (and supporting code) that are not used by Tomcat 10.1.x to support the use of OpenSSL as a replacement for JSSE to provide TLS functionality. (markt)”
>>
>> Is there a way to fix this, or has tomcat just broken everything for anyone in a RHEL environment?
>
> With tomcat-native 2.0, support for the whole APR connector is
> removed. So this also includes domain sockets since it is part of the
> APR connector. tomcat-native 2.0 now only does OpenSSL for NIO and
> NIO2.
>
> If distros are updating existing branches to tomcat-native 2.0, well,
> then they should not. 1.x is still supported.
I'm a little surprised that a distro would update to a new major version
of Tomcat Native but not update to Java 17 LTS given that Java 17 LTS
was released a good nine months before the first Tomcat Native 2.0.x
release.
My expectation would be that any distro updating to Tomcat Native 2.0.x
would also have updated to Java 17 so Tomcat users wanting to use domain
sockets can use the Java support.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: tomcat-native v2.0+ breaks unix domain socket support on java16-
Posted by Rémy Maucherat <re...@apache.org>.
On Tue, Mar 7, 2023 at 12:01 AM Graham Leggett <mi...@sharp.fm.invalid> wrote:
>
> Hi all,
>
> A while back I added unix domain socket support to tomcat-native, and patched tomcat to use it until java16 is available.
>
> Unfortunately unix domain socket support was removed from tomcat-native 2.0+, and now tomcat-native 2.0+ is appearing in distros, meaning that unix domain socket support just broke.
>
> https://tomcat.apache.org/native-doc/miscellaneous/changelog.html
>
> "Remove all API methods (and supporting code) that are not used by Tomcat 10.1.x to support the use of OpenSSL as a replacement for JSSE to provide TLS functionality. (markt)”
>
> Is there a way to fix this, or has tomcat just broken everything for anyone in a RHEL environment?
With tomcat-native 2.0, support for the whole APR connector is
removed. So this also includes domain sockets since it is part of the
APR connector. tomcat-native 2.0 now only does OpenSSL for NIO and
NIO2.
If distros are updating existing branches to tomcat-native 2.0, well,
then they should not. 1.x is still supported.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: tomcat-native v2.0+ breaks unix domain socket support on java16-
Posted by Coty Sutherland <co...@redhat.com>.
Hi there,
On Mon, Mar 6, 2023 at 6:01 PM Graham Leggett <mi...@sharp.fm.invalid>
wrote:
> Hi all,
>
> A while back I added unix domain socket support to tomcat-native, and
> patched tomcat to use it until java16 is available.
>
> Unfortunately unix domain socket support was removed from tomcat-native
> 2.0+, and now tomcat-native 2.0+ is appearing in distros, meaning that unix
> domain socket support just broke.
>
> https://tomcat.apache.org/native-doc/miscellaneous/changelog.html
>
> "Remove all API methods (and supporting code) that are not used by Tomcat
> 10.1.x to support the use of OpenSSL as a replacement for JSSE to provide
> TLS functionality. (markt)”
>
> Is there a way to fix this, or has tomcat just broken everything for
> anyone in a RHEL environment?
>
"tomcat" has broken nothing ;)
Assuming that you're using tomcat-native from EPEL 9 (because that's the
only place to get tomcat-native for RHEL at the moment), the only option is
to downgrade to the build from Aug 2022 (tomcat-native-1.2.35-1.el9). I
reopened a similar issue https://bugzilla.redhat.com/show_bug.cgi?id=2124703
to address this; please watch/engage there with any more questions/comments
(unless they are purely tomcat/tomcat-native related). Also, if you feel
that you want to document your unique problem in more detail, you can
comment or open a new bugzilla issue against Fedora EPEL 9 too.
Apologies for the inconvenience.
> Regards,
> Graham
> —
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>