[jboss-jira] [JBoss JIRA] Closed: (JBAS-6445) JBoss 5 - ServletException: OncePerRequestFilter just supports HTTP requests

JBoss 5 - ServletException: OncePerRequestFilter just supports HTTP requests ----------------------------------------------------------------------------- Key: JBAS-6445 URL: https://jira.jboss.org/jira/browse/JBAS-6445 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: Hibernate service, JMS (JBoss Messaging), JSF, Spring integration, Web (Tomcat) service, Web Services Affects Versions: JBossAS-5.0.0.GA Environment: Oracle Enterprise Linux / Redhat Linux, Sun JDK 1.5.0_14 Reporter: Prashanth N I am new to JBoss 5.0.0 although I have been using JBoss 4.2.x for a while now. We have an application built using ICEfaces, Spring and Hibernate. I have been successful in managing to make changes to the application and deploy it on JBoss 5.0.0 without any startup errors. I am using it with Sun JDK 1.5.0_14 on Linux. However, when I invoke any application URL, I get the following error: [Persistent Faces Servlet]] (http-0.0.0.0-8080-1) Servlet.service() for servlet Persistent Faces Servlet threw exception javax.servlet.ServletException: OncePerRequestFilter just supports HTTP requests at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) We are eager to move our application to JBoss 5 and we are severly gated because of the issue. If I deploy the same WAR file on 4.2.2 it works like a charm without any changes.