将项目部署到云服务器之后访问项目报错

HTTP Status 500 - The Struts dispatcher cannot be found. This is usually caused by using Struts tags without the associated filter. Struts tags are only usable when the request has passed through its servlet filter, which initializes the Struts dispatcher needed for this tag. - [unknown location]



type Exception report
message The Struts dispatcher cannot be found. This is usually caused by using Struts tags without the associated filter. Struts tags are only usable when the request has passed through its servlet filter, which initializes the Struts dispatcher needed for this tag. - [unknown location]
description The server encountered an internal error that prevented it from fulfilling this request.
exceptionorg.apache.jasper.JasperException: The Struts dispatcher cannot be found.  This is usually caused by using Struts tags without the associated filter. Struts tags are only usable when the request has passed through its servlet filter, which initializes the Struts dispatcher needed for this tag. - [unknown location]org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:565)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:481)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)javax.servlet.http.HttpServlet.service(HttpServlet.java:729)org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
root causeThe Struts dispatcher cannot be found.  This is usually caused by using Struts tags without the associated filter. Struts tags are only usable when the request has passed through its servlet filter, which initializes the Struts dispatcher needed for this tag. - [unknown location]org.apache.struts2.views.jsp.TagUtils.getStack(TagUtils.java:60)org.apache.struts2.views.jsp.StrutsBodyTagSupport.getStack(StrutsBodyTagSupport.java:44)org.apache.struts2.views.jsp.ComponentTagSupport.doStartTag(ComponentTagSupport.java:48)org.apache.jsp.index_jsp._jspx_meth_s_005faction_005f0(index_jsp.java:516)org.apache.jsp.index_jsp._jspService(index_jsp.java:195)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)javax.servlet.http.HttpServlet.service(HttpServlet.java:729)org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:443)org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:385)org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)javax.servlet.http.HttpServlet.service(HttpServlet.java:729)org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
note The full stack trace of the root cause is available in the Apache Tomcat/8.5.4 logs.