Nginx配置socket支持

最新推荐文章于 2025-03-29 21:27:00 发布

甘苦

最新推荐文章于 2025-03-29 21:27:00 发布

阅读量3.3k

点赞数

分类专栏： JavaWeb 文章标签： nginx 服务器运维

本文链接：https://blog.csdn.net/learnworm/article/details/124832134

版权

JavaWeb 专栏收录该内容

21 篇文章

订阅专栏

在尝试通过Nginx配置WebSocket支持时遇到了500 Internal Server Error。问题根源在于Servlet和相关过滤器未启用异步支持。解决方案包括在Servlet和过滤器声明中添加'<async-supported>true</async-supported>'，并确保使用Servlet 3.0以上的容器。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Nginx下配置socket支持

    server {
        listen       80;
        server_name  test.domain.com;

        # 转发站页面
        location ^~ /socket/ {
                proxy_pass http://192.168.2.10:8080/socket/;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }
        
    }

异常情况如下

HTTP Status 500 – Internal Server Error
Type 异常报告

消息 Request processing failed; nested exception is org.springframework.web.socket.sockjs.SockJsException: Uncaught failure in SockJS request, uri=http://192.168.2.10:8080/socket/online/liveness/250/2pv5gcc1/eventsource; nested exception is org.springframework.web.socket.sockjs.SockJsTransportFailureException: Failed to open session; nested exception is java.lang.IllegalArgumentException: Async support must be enabled on a servlet and for all filters involved in async request processing. This is done in Java code using the Servlet API or by adding "<async-supported>true</async-supported>" to servlet and filter declarations in web.xml. Also you must use a Servlet 3.0+ container

描述 服务器遇到一个意外的情况，阻止它完成请求。

Exception

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.web.socket.sockjs.SockJsException: Uncaught failure in SockJS request, uri=http://192.168.2.10:8080/socket/online/liveness/250/2pv5gcc1/eventsource; nested exception is org.springframework.web.socket.sockjs.SockJsTransportFailureException: Failed to open session; nested exception is java.lang.IllegalArgumentException: Async support must be enabled on a servlet and for all filters involved in async request processing. This is done in Java code using the Servlet API or by adding "<async-supported>true</async-supported>" to servlet and filter declarations in web.xml. Also you must use a Servlet 3.0+ container
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1013)
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
	org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	com.nr.base.util.lang.LangFilter.doFilter(LangFilter.java:54)
	com.nr.base.util.AuthFilter.doFilter(AuthFilter.java:56)
	org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)
	org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)
	org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
	org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
	org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:383)
	org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)
	com.nr.base.priv.shiro.filterchain.CustomShiroFilterFactoryBean$SpringShiroFilter.doFilterInternal(CustomShiroFilterFactoryBean.java:498)
	org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)
	org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:357)
	org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:270)
Root Cause