Error running the application as WAR in tomcat 9 [SPR-17599]

[spring-projects-issues]

Teh Kok How opened SPR-17599 and commented

#16725 is closed but it happens on Tomcat 9. The suggested code snippet does not work as it gives similar exception: 
| org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'endpointExporterInitializer' defined in class path resource [com/graphql/book/AppConfig.class]: Initialization of bean failed; nested exception is java.lang.RuntimeException: java.lang.IllegalStateException: javax.websocket.server.ServerContainer not available|
 
eh3rrera/graphql-java-spring-boot-example#10
graphql-java-kickstart/graphql-spring-boot#165
 
Response I get from users@tomcat.apache.org:
 
"Spring is throwing the exception. Tomcat ships with the
javax.websocket.server.ServerContainer class.

I don't believe there are any differences between Tomcat 8.5.x and
9.0.x when it comes to ClassLoader layout and class visibility.

I'd ask Spring how they are performing that sanity check to see why
they are throwing that exception."

---

Affects: 5.1.3

Issue Links:

• ServerEndpointExporter causes application context refresh to fail with an NPE when used in a Spring Boot app [SPR-12109] #16725 ServerEndpointExporter causes application context refresh to fail with an NPE when used in a Spring Boot app

[spring-projects-issues]

Juergen Hoeller commented

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")...

[spring-projects-issues]

Teh Kok How commented

I add a simple webapp/test/index.jsp with the following content:

=== start JSP ===
<%= application.getAttribute("javax.websocket.server.ServerContainer") %>
=== end JSP ===

And the page shows:

org.apache.tomcat.websocket.server.WsServerContainer@7d9225a7

[wilkinsona]

The same (I believe) problem was reported against Spring Boot (spring-projects/spring-boot#15746). I've done some initial analysis and the change in behaviour in recent versions of Tomcat 9 appears to be an ordering change in Tomcat to fix https://bz.apache.org/bugzilla/show_bug.cgi?id=62868.

[khteh]

- trunk for 9.0.13 onwards but I still see it happen iin tomcat 9.0.14

[wilkinsona]

@khteh That is what I would expect. The problem is occurring in Spring Framework due to the change in Tomcat 9.0.13.