Maybe I am making it too easy but if you or another tomcat developer could prevent the newest Tomcat from throwing this exception:
org.apache.catalina.core.StandardService.startInternal Failed to start
connector [Connector[AJP/1.3-8011]]
org.apache.catalina.LifecycleException: Der Start des
Protokoll-Handlers ist fehlgeschlagen
at
org.apache.catalina.connector.Connector.startInternal(Connector.java:1057)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:440)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:766)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Catalina.start(Catalina.java:688)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474)
Caused by: java.lang.IllegalArgumentException: The AJP Connector is
configured with secretRequired="true" but the secret attribute is either null
or "". This combination is not valid.
at
org.apache.coyote.ajp.AbstractAjpProtocol.start(AbstractAjpProtocol.java:274)
at
org.apache.catalina.connector.Connector.startInternal(Connector.java:1055)
... 12 more
This could solve the problem for me: Please just let the tomcat run through and
do not let it check for the validation criterion.
--
Florian Fritze M.A.
Fraunhofer-Informationszentrum Raum und Bau IRB
Competence Center Research Services & Open Science
Nobelstr. 12, 70569 Stuttgart, Germany
Telefon +49 711 970-2713
florian.fri...@irb.fraunhofer.de | www.irb.fraunhofer.de
-----Ursprüngliche Nachricht-----
Von: Mark Thomas <ma...@apache.org>
Gesendet: Montag, 23. März 2020 14:56
An: users@tomcat.apache.org
Betreff: Re: gostCat patch
On 23/03/2020 11:34, André Warnier (tomcat/perl) wrote:
<snip/>
> The *default* of this attribute is "false", when the "address"
> attribute is explicitly set to "127.0.0.1" or "::1", or when it
> defaults to the loopback address.
> The *default* of this attribute is "true", when the "address"
> attribute is set to any other IP address.
> unquote
<snip/>
This proposal assumes that only trusted users have access to the loopback
address. While this is true for the majority of Tomcat installations there are
use cases where this is not the case. Granted those use cases (e.g. shared
hosting) usually have better solutions (e.g. per user, isolated containers)
where only trusted users have access but not everyone uses them.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
smime.p7s
Description: S/MIME cryptographic signature
