Re: Help Needed

Mohan, On 8/5/21 23:51, Mohan T wrote: Dear All, We are using Tomcat 8.5 on Suse LINUX. We enabled JAvA security in tomcat and invoking the Catalina.sh. We are facing some permission issues in the environment. We could see the below error messages. access: access allowed ("java.util.loggin

Re: More information, Re: Tomcat 8.5.68 failing on takeoff!

James, On 8/5/21 18:33, James H. H. Lampert wrote: I finally had a chance to switch the customer back to the failing Tomcat 8.5.68, and this is what the browser error page shows (with a 500 error): Type Exception Report Message AuthConfigFactory error: java.lang.reflect.InvocationTargetExce

Help Needed

Dear All, We are using Tomcat 8.5 on Suse LINUX. We enabled JAvA security in tomcat and invoking the Catalina.sh. We are facing some permission issues in the environment. We could see the below error messages. access: access allowed ("java.util.logging.LoggingPermission" "control") java.lang.

Re: Connector Port Issue

Thank you. I will check out the info. chris On Thursday, August 5, 2021, 03:37:54 PM EDT, Peter Kreuser wrote: Chris, > Am 05.08.2021 um 18:32 schrieb Rob Sargent : > >  >>        Caused by: java.lang.IllegalArgumentException: No SSLHostConfig >>element was found with the hostName [

More information, Re: Tomcat 8.5.68 failing on takeoff!

I finally had a chance to switch the customer back to the failing Tomcat 8.5.68, and this is what the browser error page shows (with a 500 error): Type Exception Report Message AuthConfigFactory error: java.lang.reflect.InvocationTargetException Description The server encountered an unexpecte

Re: Connector Port Issue

Chris, > Am 05.08.2021 um 18:32 schrieb Rob Sargent : > >  >>Caused by: java.lang.IllegalArgumentException: No SSLHostConfig >> element was found with the hostName [_default_] to match the >> defaultSSLHostConfigName for the connector [https-jsse-nio-9443] >> > The ssl-Options are n

Re: Connector Port Issue

> Caused by: java.lang.IllegalArgumentException: No SSLHostConfig > element was found with the hostName [_default_] to match the > defaultSSLHostConfigName for the connector [https-jsse-nio-9443] > Isn’t that the real issue? --

Connector Port Issue

Trying to figure out why I'm seeing the following errors in the log. I'm sure they are the reason why I cannot connect to my server via a browser on the specified port. Any help is greatly appreciated. Tomcat 10.0.7 is running (x below are intentionally left out): catalina.out 05-Aug-2021 1

Wrong logic for NONE as certificateKeystoreFile?

It seems like the logic implemented for NONE as certificateKeystoreFile deviates from the documentation. Currently NONE is always interpreted as a file path, even for PKCS11. Looks like the comparison with NONE should be inside the parentheses for the negation? A workaround is to use "" instead of