sorry, pass dipu
On Wed, Jan 14, 2009 at 10:17 AM, Piller Sébastien <[email protected]> wrote: > Hi, > > thank you for your response. I'm well aware that increasing the post limit > size may do the trick, but this looks like a hack. What to do when something > else occurs, ie whatever IllegalStateException may be thrown at this part of > code? > > I guess the best solution will be to change the response code when such a > problem occurs. > > For the moment, I will increase the post limit to ~ 25MB, but I guess this > issue should be solved in another way. > > Does anybody may indicate me who is the offender? > > Dipu a écrit : >> >> will this be of any help >> >> >> http://stackoverflow.com/questions/123335/what-causes-java-lang-illegalstateexception-post-too-large-in-tomcat-modjk >> >> regards >> dipu >> >> On Wed, Jan 14, 2009 at 10:04 AM, Piller Sébastien <[email protected]> >> wrote: >> >>> >>> Hi everybody, >>> >>> I'm not sure if wicket has anything to do to the following issue, but >>> I'll >>> try anyway. >>> >>> I'm POSTing some large data to a wicket page (yes, there is several MB of >>> data in the post). When it is too big, I can see the following stacktrace >>> in >>> my logs: >>> >>> java.lang.IllegalStateException: Post too large >>> at >>> org.apache.catalina.connector.Request.parseParameters(Request.java:2388) >>> at org.apache.catalina.connector.Request.getParameter(Request.java:1005) >>> at >>> >>> org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:353) >>> at >>> >>> org.apache.wicket.protocol.http.servlet.ServletWebRequest.getParameter(ServletWebRequest.java:105) >>> at >>> >>> org.apache.wicket.protocol.http.request.WebRequestCodingStrategy.decode(WebRequestCodingStrategy.java:198) >>> at org.apache.wicket.Request.getRequestParameters(Request.java:171) >>> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1233) >>> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1353) >>> at org.apache.wicket.RequestCycle.request(RequestCycle.java:493) >>> at >>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:355) >>> at >>> >>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:200) >>> at >>> >>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >>> at >>> >>> org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198) >>> at >>> >>> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75) >>> at >>> >>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) >>> at >>> >>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) >>> at >>> >>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) >>> at >>> >>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) >>> at >>> >>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) >>> at >>> >>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) >>> at >>> >>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) >>> at >>> >>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) >>> at >>> >>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) >>> at >>> >>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) >>> at >>> >>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) >>> at >>> >>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) >>> at >>> >>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) >>> at java.lang.Thread.run(Thread.java:619) >>> >>> >>> I don't know exactly who catches this exception without forwarding, but >>> my >>> issue is that the page constructor doesn't get called at all (so I can't >>> add >>> some code to controll integrity) and the resonse code sent to the client >>> is >>> 200. I'm expecting that wicket or tomcat will send a response code like >>> 500: >>> Internal error or something else (anything but 200) >>> >>> Any hint? >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
