Hello Charlie,
> -Ursprüngliche Nachricht-
> Von: Charlie DiDonato
> Gesendet: Sonntag, 13. August 2023 18:08
> An: users@tomcat.apache.org
> Betreff: Java Connector help needed
>
> Hi All,
> I am migrating from tomcat 8.5x to 9.0.78
>
> Below is my server .xml
>
> I don't have Apache
Hello Peter,
> -Ursprüngliche Nachricht-
> Von: l...@kreuser.name
> Gesendet: Donnerstag, 11. Mai 2023 16:16
> An: Tomcat Users List
> Betreff: Re: Java Agent and Tomcat shutdown
>
> Hi Thomas
>
> > Am 11.05.2023 um 16:05 schrieb Thomas Hoffmann (Speed4Trade GmbH)
> :
> >
> > Hello,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 7/18/16 11:14 AM, Steffen Heil (Mailinglisten) wrote:
> Hi
>
>
>>> I am not sure that this related, be we were having issues
>>> after updating from 1.8.0_31 to 1.8.0_72 with certificates
>>> signed by root-cas that have a md5 signatur
Hi
> > I am not sure that this related, be we were having issues after
> > updating from 1.8.0_31 to 1.8.0_72 with certificates signed by
> > root-cas that have a md5 signature. While the CA signature in the CA
> > certificate does not provide any security, a bug in the jre rejected
> > the certi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 7/18/16 10:54 AM, Steffen Heil (Mailinglisten) wrote:
>> With jdk 1.8.0.45 our ldap communication is giving results. As
>> soon as we change tomcat to use jdk1.8.0_51, I am getting below
>> exception. I am not sure security changes in j
Hi
> With jdk 1.8.0.45 our ldap communication is giving results. As soon as we
> change tomcat to use jdk1.8.0_51, I am getting below
> exception. I am not sure security changes in jdk 1.8.0_51 preventing the ldap
> certificate loaded in cacerts in java not communicating
> properly to our ldap
So Tamcat has no information about the Java version to use by itself? This
is hard to believe, because the System where Tomcat is running on never had
a JAVA_HOME path defiend and Tomcat run great on it until the Java update.
Also during the Tomcat installation process the wizard asks for an Java
i
