2013/3/6 Ted <r6squee...@gmail.com>:
> Hi I'm running fedora 16, openjdk 1.7.0.9 and tomcat 7.0.37 (from a tar.gz).
>
> I'm getting a juli FileHandler problem and the existing posts / google
> search results do not appear to be the same as mine. I'm running
> tomcat freshly un-tarred from the tar.gz with catalina.sh run (not my
> webap or anything else, no changes to catalina.sh or
> logging.properties or any of the tomcat contents), so the juli jar is
> in bin and the -D logging option is what ever is in catalina.sh.
>
> I'm getting the stack trace :
>
>         [1027:/data/apps/apache-tomcat-7.0.37]catalina.sh run
>         Using CATALINA_BASE:   /data/apps/apache-tomcat-7.0.37
>         Using CATALINA_HOME:   /data/apps/apache-tomcat-7.0.37
>         Using CATALINA_TMPDIR: /data/apps/apache-tomcat-7.0.37/temp
>         Using JRE_HOME:        /data/apps/openjdk1.7.0.9
>         Using CLASSPATH:
> /data/apps/apache-tomcat-7.0.37/bin/bootstrap.jar:/data/apps/apache-tomcat-7.0.37/bin/tomcat-juli.jar
>         Can't load log handler "1catalina.org.apache.juli.FileHandler"
>         java.lang.ClassNotFoundException: 
> 1catalina.org.apache.juli.FileHandler
>         java.lang.ClassNotFoundException: 
> 1catalina.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)
>

Any more lines in the stack trace?
It certainly looks like a work of default JRE's
java.util.logging.LogManager implementation.

That is as if  -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
 setting was not effective.
It reads the correct file though, so the file name was passed successfully.

You may try to simplify the logging.properties file so that it
conforms to the format expected by the default LogManager.  That is,
remove all loggers with numerical prefixes and leave only
ConsoleLogger there.

That way you can get working logging and try to start Tomcat and see
whether it fails further along the way (e.g. whether it can load other
classes from tomcat-juli.jar).

>
> I should note that the above works when I use oracle-jdk1.7.0_17. I'm
> suspecting this is a problem with openjdk but more like a "configure
> openjdk to work with tomcat" issue.
>
> Does anyone know what configuration changes need to be made to openjdk
> to work with tomcat's juli logger?
>

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to