Can you share with me your JSP for test? Thanks. On Fri, Dec 14, 2018 at 7:50 PM Mark Thomas <ma...@apache.org> wrote:
> On 14/12/2018 11:15, Kok How Teh wrote: > >> Have you configued "containerSciFilter" on the Context? > > No. I don't > > > >> Have you removed any JARs from Tomcat's lib directory? > > These are what I have in the lib: > > > > /opt/tomcat/latest/lib 2114 $ ls > > annotations-api.jar catalina.jar ecj-4.7.3a.jar jasper.jar > > servlet-api.jar tomcat-dbcp.jar tomcat-i18n-ja.jar > > tomcat-jni.jar tomcat-websocket.jar > > catalina-ant.jar catalina-storeconfig.jar el-api.jar > > jaspic-api.jar tomcat-api.jar tomcat-i18n-es.jar tomcat-i18n-ru.jar > > tomcat-util.jar websocket-api.jar > > catalina-ha.jar catalina-tribes.jar jasper-el.jar > jsp-api.jar > > tomcat-coyote.jar tomcat-i18n-fr.jar tomcat-jdbc.jar > > tomcat-util-scan.jar > > > >> Are you using embedded without the WebSocket JAR? > > How do I check this? > > Given the above, this does not apply to you. > > Time to create the simplest possible test case that demonstrates this > problem on a clean Tomcat 9.0.14 install. I suggest starting with the > JSP I used for my test. You'll probably figure out what the problem is > by creating the test case. > > Mark > > > > > > On Fri, Dec 14, 2018 at 4:38 PM Mark Thomas <ma...@apache.org> wrote: > > > >> On 14/12/2018 00:34, Kok How Teh wrote: > >>> I filed a bug at Spring JIRA and this is the response I get ( > >>> https://jira.spring.io/browse/SPR-17599): > >>> > >>> There seems to be a misunderstanding in that conversation on the Tomcat > >>> mailing list: It's not that we can't find the class of the name > >>> javax.websocket.server.ServerContainer, it's the *ServletContext > >>> attribute* with > >>> name "javax.websocket.server.ServerContainer" that we can't find. In > >> other > >>> words, we can't find a pre-initialized WebSocket container instance. > >>> > >>> So the root of the problem you can easily reproduce without Spring: > >> Simply > >>> implement a Servlet and check the return value of > >>> > >> > getServletContext().getAttribute("javax.websocket.server.ServerContainer") > >>> ... > >> > >> Tomcat creates that automatically unless you explicitly disable the > >> ServletContainerInitializer. > >> > >> A web app with a single JSP (below) deployed to a clean Tomcat 9.0.x > >> install shows this is the case. > >> > >> === start JSP === > >> <%= application.getAttribute("javax.websocket.server.ServerContainer") > %> > >> === end JSP === > >> > >> Have you configued "containerSciFilter" on the Context? > >> > >> Have you removed any JARs from Tomcat's lib directory? > >> > >> Are you using embedded without the WebSocket JAR? > >> > >> Mark > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
