Based on those errors, it sounds like SHA-1 has been desupported in the
newer OpenJDK version.
On Wed, Feb 16, 2022 at 1:55 PM Robert Hicks wrote:
> We are currently running Tomcat 9.0.40 and OpenJDK (Red Hat) 1.8.0_292 and
> have no issues.
>
> We upgrade to the ones in the subject line and Tom
We are currently running Tomcat 9.0.40 and OpenJDK (Red Hat) 1.8.0_292 and
have no issues.
We upgrade to the ones in the subject line and Tomcat throws "SHA1PRNG
SecureRandom not available" and "SHA MessageDigest not available" and
"SHA-1 not available" and others.
We downgrade to .40 and _292 an
Hello Stefan,
the debug output of mod_jk shows at least which route the request is going:
[info] jk_handler::mod_jk.c (2968): No body with status=401 for
worker=ajp13_worker
So it looks like that the code
https://github.com/apache/tomcat-connectors/blob/main/native/apache-2.0/mod_jk.c#L2954#L29
Glad you figured it out!
Thank you,
Neil
--
Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com
We offer 30 year loans on single family houses!
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For addition
ср, 16 февр. 2022 г. в 13:51, Blake McBride :
>
> Problem solved!
>
> I am quite embarrassed because I've had this problem before, solved it
> (with the help of this list), and documented it. Here are my notes:
>
> tomcat slow startup
>
> The secure random calls may be blocking as there is not eno
Problem solved!
I am quite embarrassed because I've had this problem before, solved it
(with the help of this list), and documented it. Here are my notes:
tomcat slow startup
The secure random calls may be blocking as there is not enough entropy to
feed them in /dev/random.
Change /etc/java-8-
