Process or in-service induced imperfections, mechanical joints (welds, solved, cemented

Is able to detect imperfections of the material failure of metallurgical or technological Which allow escaping of liquids (in presence of the pressure gradient). Leakage testing is focused on the detection of the imperfections in the solid boundary-line, On the JBoss jira I spotted a similar issue where somebody used different versions but had the same problem. I have tested this with the Apache Native Library v1.2.17, Tomcat v9.0.12, APR v1.5.2 and JDK v1.8.0_181 running on an Ubuntu 16.04.5 server. When we turned off the client certificate validation by either commenting out the call to X509_verify_cert in OpenSSL (which in turn calls Tomcat Native's SSL_callback_SSL_verify that performs the OCSP checks) or setting SSLVerif圜lient to 'none' and clientAuth to 'false' in the APR connector the server did not run out of memory and the graph of available memory flatlines. Afterwards we tried the same thing with smaller Comodo certificates (see figure 2) which has the same result but takes a longer time (15 hours).

In figure 1, showing the available server memory, you can see that using these larger PKIoverheid certificates the server runs out of memory every 2,5 - 3 hours. We first noticed the problem with the PKIoverheid certificates, which are larger in size than the Comodo certificates. We have tested this with two types of client certificates from two different root CA's: PKIoverheid (the root certificate of the Dutch national government) and Comodo certificates, both containing OCSP urls. The application we created is queried often (every second by two simultaneous clients). We've noticed a gradual increase in the memory consumed by the Java process until the system runs out of memory and the OOM-killer we configured kills and restarts the process. We are using the Tomcat APR connector in our application to perform client-certificate validation with OCSP checks.

Comodo leak test