2015-03-13 23:43 GMT+03:00 Graham Leggett <minf...@sharp.fm>: > On 13 Mar 2015, at 9:58 PM, Neven Cvetkovic <neven.cvetko...@gmail.com> wrote: > >> Just to confirm, the 403 Forbidden page was rendered by Tomcat, not Apache >> HTTPD? > > Yes, it is branded tomcat and appears in the tomcat access log. > >> I don't expect it is an Apache issue here - because you mentioned your >> application worked before - I assume with the same URL, and no updates to >> Apache HTTPD configuration. >> >> Next thing I would probably increase the verbosity of the Realm logging, by >> updating your conf/logging.properties, e.g. >> org.apache.catalina.realm.level = ALL >> org.apache.catalina.realm.useParentHandlers = true >> org.apache.catalina.authenticator.level = ALL >> org.apache.catalina.authenticator.useParentHandlers = true >> >> >> You might want to disable buffering as well, e.g. >> 1catalina.org.apache.juli.FileHandler.bufferSize = -1 > > None of these changes to logging.properties have any effect on my test system > of tomcat v7.0.59 deployed to RHEL6. I get no changes to catalina.out at all, > it stays completely silent. > > I tried to make the same changes to a tomcat v7.0.59 running within Eclipse, > and in this case I get the following: > > Can't load log handler "2localhost.org.apache.juli.FileHandler" > java.lang.ClassNotFoundException: 2localhost.org.apache.juli.FileHandler > java.lang.ClassNotFoundException: 2localhost.org.apache.juli.FileHandler > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > at java.util.logging.LogManager$3.run(LogManager.java:418)
You are using JRE's default java.util.logging.LogManager. You need to configure JRE to use the Tomcat JULI implementation of log manager with -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager The JRE class is usable, but its logging.properties format is a bit different. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
