Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Vaadin 7.6.0 and Jetty 6 (servlet 2.5 compatible)
Hi all,
is Vaadin 7.6.0 compatible with Jetty 6 (which, in turn, is only compatible with libservlet2.5-api)?
I just upgraded an application from Vaadin 7.3.x to 7.6.0 and I get this error in the log file:
2016-01-05 17:41:28.715:INFO::jetty-6.1.24
2016-01-05 17:41:28.766:INFO::Deploy /etc/jetty/contexts/javadoc.xml -> org.mortbay.jetty.handler.ContextHandler@58ecb281{/javadoc,file:/usr/share/jetty/javadoc}
2016-01-05 17:41:28.810:INFO::Deploy /etc/jetty/contexts/demo_reportmachine.xml -> org.mortbay.jetty.webapp.WebAppContext@2d58f9d3{/,/usr/share/jetty/webapps/demo_reportmachi$
2016-01-05 17:41:28.818:INFO::Deploy /etc/jetty/contexts/reportmachine.xml -> org.mortbay.jetty.webapp.WebAppContext@2c79a2e7{/,/usr/share/jetty/webapps/reportmachine.war}
2016-01-05 17:41:28.842:INFO::Extract /usr/share/jetty/webapps/demo_reportmachine.war to /var/cache/jetty/data/Jetty_localhost_8080_demo_reportmachine.war___demo.reportmachin$
2016-01-05 17:41:32.833:INFO::NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
2016-01-05 17:41:33.207:INFO::Extract /usr/share/jetty/webapps/reportmachine.war to /var/cache/jetty/data/Jetty_localhost_8080_reportmachine.war___reportmachine.marcozanon.co$
2016-01-05 17:41:41.613:WARN::failed jsp: java.lang.NoClassDefFoundError: javax/servlet/jsp/JspFactory
2016-01-05 17:41:41.614:WARN::failed org.mortbay.jetty.webapp.WebAppContext@2c79a2e7{/,/usr/share/jetty/webapps/reportmachine.war}: java.lang.NoClassDefFoundError: javax/serv$
2016-01-05 17:41:41.633:INFO::NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
2016-01-05 17:41:41.643:WARN::failed ContextHandlerCollection@477a1767: java.lang.NoClassDefFoundError: javax/servlet/jsp/JspFactory
2016-01-05 17:41:41.645:INFO::Opened /var/log/jetty/2016_01_05.request.log
2016-01-05 17:41:41.645:WARN::failed HandlerCollection@20968fda: java.lang.NoClassDefFoundError: javax/servlet/jsp/JspFactory
2016-01-05 17:41:41.645:WARN::Error starting handlers
java.lang.NoClassDefFoundError: javax/servlet/jsp/JspFactory
at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:77)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:685)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Marco Zanon: Hi all,
is Vaadin 7.6.0 compatible with Jetty 6 (which, in turn, is only compatible with libservlet2.5-api)?
I just upgraded an application from Vaadin 7.3.x to 7.6.0 and I get this error in the log file:
Hey Marco, I am running 7.6.0 on Jetty 6.1.4, it's working fine for me without changing anything upgrading from 7.5.x!
Thanks Mario, then I know that Vaadin 7.6.0 is perfectly fine with Jetty 6. It must be a compilation problem then.
Thanks,
Marco
After hours of debugging, I found out that the problem was due to Tomcat7 (used locally when developing, in place of Jetty6 used on the vps) whose libraries in /usr/share/java probably interfered during the compilation.
Installing Jetty6 and removing Tomcat7 locally solved my problems.
Also, installing libjetty-java AND libjetty-java-extra made the logging system in Jetty6 started to work again.
Thanks,
Marco