https://bz.apache.org/bugzilla/show_bug.cgi?id=61210
Bug ID: 61210
Summary: When using the Security Manager, Tomcat prints warning
about a non-existent file
Product: Tomcat 8
Version: 8.5.x-trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Util
Assignee: dev@tomcat.apache.org
Reporter: csuth...@redhat.com
Target Milestone: ----
I noticed that when using the Security Manager in Tomcat you always see the
following warning messages on startup (one for every application that's
deployed):
~~~
WARNING [localhost-startStop-1]
org.apache.juli.ClassLoaderLogManager.readConfiguration Reading
/apache-tomcat-8.5.15/webapps/ROOT/WEB-INF/classes/logging.properties is not
permitted. See "per context logging" in the default catalina.policy file.
WARNING [localhost-startStop-1]
org.apache.juli.ClassLoaderLogManager.readConfiguration Reading
/apache-tomcat-8.5.15/webapps/examples/WEB-INF/classes/logging.properties is
not permitted. See "per context logging" in the default catalina.policy file.
WARNING [localhost-startStop-1]
org.apache.juli.ClassLoaderLogManager.readConfiguration Reading
/apache-tomcat-8.5.15/webapps/docs/WEB-INF/classes/logging.properties is not
permitted. See "per context logging" in the default catalina.policy file.
~~~
While the message is technically accurate (reading the file is prohibited), it
isn't pertinent to the user because the file may not (doesn't in this case)
exist in any of these three applications. Is it possible to check that the file
exists at this point so that we can only print the message when it's present?
Do so would remove an extra warning (that may not be applicable) from the log
file and give users a clean vanilla log to start with.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
