NoClassDefFoundError

On a AWS instance (Redhat) I’m seeing this in the server log from a maven package installation, which suggests a problem with the classpath, but this is all set in the fess.sh/fess.in.sh file. Wondered if anyone had seen it before or can suggest a fix.

I simply ran:
mvn antrun:run
mvn package

Cheers!

Feb 27, 2020 9:28:52 PM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter [encodingFilter]
java.lang.NoClassDefFoundError: Could not initialize class org.lastaflute.web.servlet.filter.LastaPrepareFilter
at org.codelibs.fess.filter.EncodingFilter.init(EncodingFilter.java:56)
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:270)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:251)
at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:102)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4533)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5172)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:467)
at org.dbflute.tomcat.TomcatBoot.startServer(TomcatBoot.java:713)
at org.dbflute.tomcat.TomcatBoot.go(TomcatBoot.java:402)
at org.dbflute.tomcat.TomcatBoot.bootAwait(TomcatBoot.java:347)
at org.codelibs.fess.FessBoot.main(FessBoot.java:96)

Can anyone help - this is unchanged checked out code building the zip and then unzipping annd simply trying to run fess.sh
On Redhat and osx. Looks like tomcat is ignoring any start of the underlying fess app.
There is nothing in fess.log just the server log as above.

Argh! This was a clash between the compile JDK version and the runtime. Doh!