|
Re: "Form Too Large" with Custom Widget [message #93965 is a reply to message #93935] |
Thu, 19 June 2008 07:06 |
Eclipse User |
|
|
|
Originally posted by: rherrmann.innoopract.com
Tiago,
Jetty seems to limit the maximum form content by default.
Is there a server-side exception you are getting? If so, please send
the stack trace (start with -consolelog to have it printed to std out).
Cheers,
Rüdiger
Tiago wrote:
> Hi
>
> I have a custom widget that generates quite a big amount of data that I
> want to send back to the java part I'm using the following snippet:
>
> var wm = org.eclipse.swt.WidgetManager.getInstance();
> var id = wm.findIdByWidget(this);
> var req = org.eclipse.swt.Request.getInstance();
> req.addParameter(id + ".customparameter", this._bigstring);
>
> But I'm getting a blank screen with a message saying "Form Too Large".
> Any ideias of how can I overcome this?
>
> Thanks in advance.
>
> Tiago
|
|
|
|
Re: "Form Too Large" with Custom Widget [message #94006 is a reply to message #93978] |
Thu, 19 June 2008 12:26 |
Eclipse User |
|
|
|
Originally posted by: rherrmann.innoopract.com
Tiago,
this looks like you hit the default limit for form requests of Jetty.
See this link on how this limit can be changed:
http://www.nabble.com/Tap4-and-Jetty-%22Form-Too-Large%22-to 11029080.html
However, I would rather work on reducing the size of the request.
HTH
Rüdiger
Tiago wrote:
> Hi Rudige,
>
> This is what I got in the server side:
>
> ------------------------------------------------------------ ------------------------------------------
>
>
> 19 Jun 2008 12:01:51,884 ERROR org.mortbay.jetty.context./ -
> /chums?nocache=1213873311852:
> java.lang.IllegalStateException: Form too large
> at org.mortbay.http.HttpRequest.extractParameters(HttpRequest.j ava:877)
> at org.mortbay.http.HttpRequest.getParameter(HttpRequest.java:9 44)
> at
> org.mortbay.jetty.servlet.ServletHttpRequest.getParameter(Se rvletHttpRequest.java:650)
>
> at
> javax.servlet.ServletRequestWrapper.getParameter(ServletRequ estWrapper.java:138)
>
> at
> org.eclipse.rwt.internal.service.ServiceManager.getCustomHan dlerId(ServiceManager.java:128)
>
> at
> org.eclipse.rwt.internal.service.ServiceManager.isCustomHand ler(ServiceManager.java:116)
>
> at
> org.eclipse.rwt.internal.service.ServiceManager$HandlerDispa tcher.service(ServiceManager.java:96)
>
> at
> org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelega te.java:61)
> at
> org.eclipse.ui.internal.servlet.RequestHandler.service(Reque stHandler.java:52)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
>
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
> org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:270)
>
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:428)
> at
> org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHan dler.java:677)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:568)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> at org.mortbay.http.HttpServer.service(HttpServer.java:909)
> at org.mortbay.http.HttpConnection.service(HttpConnection.java: 820)
> at org.mortbay.http.HttpConnection.handleNext(HttpConnection.ja va:986)
> at org.mortbay.http.HttpConnection.handle(HttpConnection.java:8 37)
> at
> org.mortbay.http.SocketListener.handleConnection(SocketListe ner.java:245)
> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:3 57)
> at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:5 34)
>
> ------------------------------------------------------------ ------------------------------------------
>
>
> It doesn't say me much, maybe will do for you.
>
> Thanks.
>
> Tiago
>
> Rüdiger Herrmann wrote:
>> Tiago,
>>
>> Jetty seems to limit the maximum form content by default.
>> Is there a server-side exception you are getting? If so, please send
>> the stack trace (start with -consolelog to have it printed to std out).
>>
>> Cheers,
>> Rüdiger
>>
>> Tiago wrote:
>>> Hi
>>>
>>> I have a custom widget that generates quite a big amount of data that
>>> I want to send back to the java part I'm using the following snippet:
>>>
>>> var wm = org.eclipse.swt.WidgetManager.getInstance();
>>> var id = wm.findIdByWidget(this);
>>> var req = org.eclipse.swt.Request.getInstance();
>>> req.addParameter(id + ".customparameter", this._bigstring);
>>>
>>> But I'm getting a blank screen with a message saying "Form Too
>>> Large". Any ideias of how can I overcome this?
>>>
>>> Thanks in advance.
>>>
>>> Tiago
|
|
|
Re: "Form Too Large" with Custom Widget [message #94097 is a reply to message #94006] |
Fri, 20 June 2008 13:04 |
Tiago Messages: 55 Registered: July 2009 |
Member |
|
|
Hi Rüdiger,
That will do it. Thanks.
Tiago
Rüdiger Herrmann wrote:
> Tiago,
>
> this looks like you hit the default limit for form requests of Jetty.
>
> See this link on how this limit can be changed:
> http://www.nabble.com/Tap4-and-Jetty-%22Form-Too-Large%22-to 11029080.html
>
> However, I would rather work on reducing the size of the request.
>
> HTH
> Rüdiger
>
> Tiago wrote:
>> Hi Rudige,
>>
>> This is what I got in the server side:
>>
>> ------------------------------------------------------------ ------------------------------------------
>>
>>
>> 19 Jun 2008 12:01:51,884 ERROR org.mortbay.jetty.context./ -
>> /chums?nocache=1213873311852:
>> java.lang.IllegalStateException: Form too large
>> at
>> org.mortbay.http.HttpRequest.extractParameters(HttpRequest.j ava:877)
>> at org.mortbay.http.HttpRequest.getParameter(HttpRequest.java:9 44)
>> at
>> org.mortbay.jetty.servlet.ServletHttpRequest.getParameter(Se rvletHttpRequest.java:650)
>>
>> at
>> javax.servlet.ServletRequestWrapper.getParameter(ServletRequ estWrapper.java:138)
>>
>> at
>> org.eclipse.rwt.internal.service.ServiceManager.getCustomHan dlerId(ServiceManager.java:128)
>>
>> at
>> org.eclipse.rwt.internal.service.ServiceManager.isCustomHand ler(ServiceManager.java:116)
>>
>> at
>> org.eclipse.rwt.internal.service.ServiceManager$HandlerDispa tcher.service(ServiceManager.java:96)
>>
>> at
>> org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelega te.java:61)
>> at
>> org.eclipse.ui.internal.servlet.RequestHandler.service(Reque stHandler.java:52)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistratio n.handleRequest(ServletRegistration.java:90)
>>
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce ssAlias(ProxyServlet.java:111)
>>
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi ce(ProxyServlet.java:59)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>> at
>> org.eclipse.equinox.http.jetty.internal.HttpServerManager$In ternalHttpServiceServlet.service(HttpServerManager.java:270)
>>
>> at
>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder .java:428)
>> at
>> org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHan dler.java:677)
>>
>> at
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandl er.java:568)
>> at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
>> at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
>> at org.mortbay.http.HttpServer.service(HttpServer.java:909)
>> at org.mortbay.http.HttpConnection.service(HttpConnection.java: 820)
>> at
>> org.mortbay.http.HttpConnection.handleNext(HttpConnection.ja va:986)
>> at org.mortbay.http.HttpConnection.handle(HttpConnection.java:8 37)
>> at
>> org.mortbay.http.SocketListener.handleConnection(SocketListe ner.java:245)
>> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:3 57)
>> at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:5 34)
>>
>> ------------------------------------------------------------ ------------------------------------------
>>
>>
>> It doesn't say me much, maybe will do for you.
>>
>> Thanks.
>>
>> Tiago
>>
>> Rüdiger Herrmann wrote:
>>> Tiago,
>>>
>>> Jetty seems to limit the maximum form content by default.
>>> Is there a server-side exception you are getting? If so, please send
>>> the stack trace (start with -consolelog to have it printed to std out).
>>>
>>> Cheers,
>>> Rüdiger
>>>
>>> Tiago wrote:
>>>> Hi
>>>>
>>>> I have a custom widget that generates quite a big amount of data
>>>> that I want to send back to the java part I'm using the following
>>>> snippet:
>>>>
>>>> var wm = org.eclipse.swt.WidgetManager.getInstance();
>>>> var id = wm.findIdByWidget(this);
>>>> var req = org.eclipse.swt.Request.getInstance();
>>>> req.addParameter(id + ".customparameter", this._bigstring);
>>>>
>>>> But I'm getting a blank screen with a message saying "Form Too
>>>> Large". Any ideias of how can I overcome this?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Tiago
|
|
|
Powered by
FUDForum. Page generated in 0.01516 seconds