Hi, Dan.
Latest commit made that upgrades Jetty to 9.2 introduces a issue to those using
the generated WAR file “as is" on Tomcat.
It fails with the following exception:
GRAVE: Error during ServletContainerInitializer processing
javax.servlet.ServletException: Not running on Jetty, JSR-356 support
unavailable
at
org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:146)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5513)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecuto
Simply removing the " jetty-all-9.2.11.v20150529.jar” jar from the WAR avoids
it.
On [1] seems there’s a way to avoid it by defining a property the WebAppContext.
Might it be better managed through Maven ?
HTH,
Oscar
[1] http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html
<http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04207.html>
