On 6/27/25 10:04 AM, Michael Osipov wrote:
On 2025/06/26 11:52:22 jean-frederic clere wrote:
Hi,
While using main I have:
+++
26-Jun-2025 12:00:18.247 SEVERE [main]
org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
initialize component [Connector["http-apr-8080"]]
java.lang.UnsatisfiedLinkError: 'long
org.apache.tomcat.jni.Address.info(java.lang.String, int, int, int, long)'
at org.apache.tomcat.jni.Address.info(Native Method)
at
org.apache.tomcat.util.net.AprEndpoint.bind(AprEndpoint.java:392)
+++
This is expected, no? Since the AprConnector has been removed, but I would
expect that the listener would wring an error during startup . Did you check?
+++
27-Jun-2025 11:39:54.661 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
Apache Tomcat Native library [2.0.9-dev] using APR version [1.7.5].
27-Jun-2025 11:39:54.661 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
capabilities: IPv6 [true], sendfile [true], accept filters [false],
random [true], UDS [true].
27-Jun-2025 11:39:54.661 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL
configuration: useAprConnector [false], useOpenSSL [true]
27-Jun-2025 11:39:54.663 INFO [main]
org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
successfully initialized [OpenSSL 3.2.4 11 Feb 2025]
27-Jun-2025 11:39:54.832 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["http-nio-8080"]
27-Jun-2025 11:39:54.843 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["https-openssl-apr-8444"]
27-Jun-2025 11:39:54.844 SEVERE [main]
org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
initialize component [Connector["https-openssl-apr-8444"]]
java.lang.UnsatisfiedLinkError: 'long
org.apache.tomcat.jni.Address.info(java.lang.String, int, int, int, long)'
+++
So no warning, but yes 2.0.x doesn't support apr connector, we might
warn earlier,
When using 1.3.x the JVM was crashing I "fixed" that now I have:
+++
Caused by: javax.crypto.BadPaddingException: Given final block
not properly padded. Such issues can arise if a bad key is used during
decryption.
at
java.base/com.sun.crypto.provider.CipherCore.unpad(CipherCore.java:861)
at
java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(CipherCore.java:941)
at
java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:734)
at
java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446)
at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2244)
+++
I was expecting openssl asking for the passphrase but it seems that is
not possible now.
How so, if you use JSSE here? Did you check that you really use OpenSSL instead
of JSSE?
Tomcat says: https-openssl-apr-8444 according to the trace so yes.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
--
Cheers
Jean-Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
