https://issues.apache.org/bugzilla/show_bug.cgi?id=56776
--- Comment #2 from George Sexton <gsex...@mhsoftware.com> --- I looked at this some more. The issue seems to be tied to having an empty logging.properties. If you're running under the security manager, with log4j, and you specify an empty java.util.logging.config.file, the error will happen. The simplest solution is to not specify -Djava.util.logging.config.file=empty file on the command line. I can reproduce it in a simple test case. -- 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
