• Sign In
  1. Messages

javax.servlet.ServletException: Filter execution threw an exception

LabKey Support Forum (Inactive)

View Message

view list print
javax.servlet.ServletException: Filter execution threw an exception bill c white  2014-10-16 12:20
Status: Closed
 
I have tried two different systems now, one an upgrade to several successive upgraded versions of the LabKey code distributions, and one on a fresh system, and I get the same stack trace. It means nothing to me. Nothing in the logs gives me any hints. Ideas? Both systems are running Debian 7, Java 7 and Tomcat 7.

type Exception report

message Filter execution threw an exception

description The server encountered an internal error (Filter execution threw an exception) that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Filter execution threw an exception
root cause

java.lang.ExceptionInInitializerError
    org.labkey.api.util.ExceptionUtil.handleException(ExceptionUtil.java:462)
    org.labkey.api.util.ExceptionUtil.handleException(ExceptionUtil.java:456)
    org.labkey.api.security.AuthFilter.doFilter(AuthFilter.java:74)
root cause

java.lang.NullPointerException
    org.labkey.api.module.ModuleResourceCaches$StandardModuleResourceDirectory.<init>(ModuleResourceCaches.java:102)
    org.labkey.api.module.ModuleResourceCaches$StandardModuleResourceDirectory.<init>(ModuleResourceCaches.java:89)
    org.labkey.api.module.ModuleResourceCaches.createModuleResourceDirectory(ModuleResourceCaches.java:85)
    org.labkey.api.module.ModuleResourceCaches.create(ModuleResourceCaches.java:51)
    org.labkey.api.data.DbScope.<clinit>(DbScope.java:104)
    org.labkey.api.util.ExceptionUtil.handleException(ExceptionUtil.java:462)
    org.labkey.api.util.ExceptionUtil.handleException(ExceptionUtil.java:456)
    org.labkey.api.security.AuthFilter.doFilter(AuthFilter.java:74)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.28 logs.
 
 
jeckels responded:  2014-10-16 13:00
Hi Bill,

Sorry to hear about the errors. It's likely that there's some other upstream error that's the true root cause of these problems. Can you ZIP up the contents of your %TOMCAT_HOME%/logs directory and post them here? Hopefully one of the messages will give us some clues.

Thanks,
Josh
 
adam responded:  2014-10-16 13:10
For what it's worth, in Subversion commit r34456 I fixed our start-up time exception handling to correctly display the initial, underlying exception on the first page render. This won't help you in the near-term, since my change is in our upcoming 14.3 release. Please do let us know what the earlier exception is.

Adam
 
jeckels responded:  2014-10-16 23:23
Hi Bill,

In the logs you sent us, I found this error message:

Caused by: java.lang.UnsupportedClassVersionError: org/labkey/bootstrap/LabkeyServerBootstrapClassLoader : Unsupported major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

That's a Java 7 class file format, and indicates that you might be running Tomcat with an older Java release. Can you confirm that Tomcat is pointed at a Java 7 installation?

Additionally, catalina.out contained this error:

java.io.FileNotFoundException: /usr/share/tomcat7/logs/labkey.log (No such file or directory)

Can you check if the directory /usr/share/tomcat7/logs exists? Does that look like the right directory for your Tomcat deployment? Perhaps the CATALINA_HOME environment variable is not set correctly?

Also, what version of LabKey Server are you attempting to install? 14.2?

Thanks,
Josh