Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Martin Grigorov
Hi, On Thu, Jun 20, 2013 at 10:11 PM, Marios Skounakis msc...@gmail.com wrote: Hi all, I have the following problem: - User submits form with lots of textareas via ajax - User gets a blank page I think (but I'm not quite sure yet) this happens when the textareas contain so much text

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Marios Skounakis
Some more info after further investigation: The problem is definitely related to tomcat maxPostSize parameter. I have set this to a very small value (100) and the problem is occurring even in very small regular (non ajax) form posts. Debugging this I found that

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Martin Grigorov
You can use Wicket API to set the maxSize - org.apache.wicket.markup.html.form.Form#setMaxSize This way Tomcat will read the whole input and Wicket will report the error. But maybe reading the whole input is what you try to avoid. On Fri, Jun 21, 2013 at 11:24 AM, Marios Skounakis

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Marios Skounakis
Actually I want to read the whole input, and increasing tomcat maxPostSize is the solution. But I was puzzled by the fact that I got no exception and instead I got this weird behavior. Is there something that wicket does that keeps tomcat from throwing the exception? On Fri, Jun 21, 2013 at

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Martin Grigorov
On Fri, Jun 21, 2013 at 11:44 AM, Marios Skounakis msc...@gmail.com wrote: Actually I want to read the whole input, and increasing tomcat maxPostSize is the solution. But I was puzzled by the fact that I got no exception and instead I got this weird behavior. Is there something that wicket

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Marios Skounakis
Looking at tomcat sources it seems tomcat does not throw an exception bug simply logs a debug message! Regarding wicket now, setting Form#setMaxSize seems to have no effect unless there is a file upload involved. My case has just lots of textareas with lots of text content... Can you please

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Martin Grigorov
On Fri, Jun 21, 2013 at 12:29 PM, Marios Skounakis msc...@gmail.com wrote: Looking at tomcat sources it seems tomcat does not throw an exception bug simply logs a debug message! Regarding wicket now, setting Form#setMaxSize seems to have no effect unless there is a file upload involved. My

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-21 Thread Marios Skounakis
Martin, Thank you for your replies. You are right that using MultipartServletWebRequestImpl you can set the max size and handle the error. Cheers Marios On Fri, Jun 21, 2013 at 2:09 PM, Martin Grigorov mgrigo...@apache.orgwrote: On Fri, Jun 21, 2013 at 12:29 PM, Marios Skounakis

RE: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-20 Thread Paul Bors
Stack trace? -Original Message- From: Marios Skounakis [mailto:msc...@gmail.com] Sent: Thursday, June 20, 2013 4:12 PM To: users@wicket.apache.org Subject: Ajax form submit and Tomcat maxPostSize/connectionTimeout Hi all, I have the following problem: - User submits form with lots of

Re: Ajax form submit and Tomcat maxPostSize/connectionTimeout

2013-06-20 Thread Paul BorČ™
Blank form prob means empty model objects. Start Wicket in DEVELOPMENT mode: https://cwiki.apache.org/WICKET/faqs.html#FAQs-Myapplicationsays%2522DEVELOPMENTMODE%2522%252ChowdoIswitchtoproduction%253F Add the DebugBar to your page: