Sorry for taking so "looong" :) could you open a issue for this at ops4j? thanks, Achim
2012/12/17 Bengt Rodehav <[email protected]> > I've made some more research. I found this line in Jetty's ContexHandler > class: > > * private int _maxFormContentSize = > Integer.getInteger("org.eclipse.jetty.server.Request.maxFormContentSize",200000).intValue(); > * > > This implies that the default value is taken from a system property. So, I > set that system property to a higher value and it worked. I guess this is a > good-enough workaround for me. > > I think it should also be possible to override the system property by > setting the corresponding attribute on the server. But adding the following > does not seem to work: > > <Call name="setAttribute"> > <Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg> > <Arg>2000000</Arg> > </Call> > > I think that in a "normal" Jetty server this would work but I can't seem > to get it to work with Pax-Web. > > The issue with not reading the jetty configuration file when you provide > your own org.ops4j.pax.web.cfg I believe must be fixed. > > /Bengt > > > 2012/12/17 Bengt Rodehav <[email protected]> > >> Perfect - it makes life easier, >> >> /Bengt >> >> >> 2012/12/17 Achim Nierbeck <[email protected]> >> >>> Hi Bengt, >>> >>> Pax-Web does use the Metadata service. >>> >>> regards, Achim >>> >>> >>> 2012/12/17 Bengt Rodehav <[email protected]> >>> >>>> Good idea, >>>> >>>> I already have my own org.ops4j.pax.web.cfg but it's easy to forget to >>>> include the org.ops4j.pax.web.config.file attribute causing jetty.xml >>>> not to be used at all. >>>> >>>> BTW do you use the metadata services? If not, I suggest to do so since >>>> it's then easy to look at the configuration in the web console and see all >>>> possible values. >>>> >>>> /Bengt >>>> >>>> >>>> 2012/12/17 Jean-Baptiste Onofré <[email protected]> >>>> >>>>> FYI, in order to give more "visibility" to the users: >>>>> >>>>> https://issues.apache.org/**jira/browse/KARAF-2053<https://issues.apache.org/jira/browse/KARAF-2053> >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> On 12/17/2012 07:55 AM, Bengt Rodehav wrote: >>>>> >>>>>> Thanks for the advice Freeman - I'll think about that. >>>>>> >>>>>> /Bengt >>>>>> >>>>>> >>>>>> 2012/12/17 Freeman Fang <[email protected] >>>>>> <mailto:[email protected]**>> >>>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> As you also have your own etc/org.ops4j.pax.web.cfg, it means it >>>>>> will override the configuration for http feature >>>>>> <config name="org.ops4j.pax.web"> >>>>>> org.osgi.service.http.port=**8181 >>>>>> javax.servlet.context.tempdir=** >>>>>> ${karaf.data}/pax-web-jsp >>>>>> org.ops4j.pax.web.config.file=** >>>>>> ${karaf.base}/etc/jetty.xml >>>>>> </config> >>>>>> >>>>>> So you need ensure your own etc/org.ops4j.pax.web.cfg has >>>>>> something like >>>>>> org.ops4j.pax.web.config.file=**Your_karaf_kit_path/etc/jetty.** >>>>>> xml >>>>>> >>>>>> So that the etc/jetty.xml could be picked up. >>>>>> >>>>>> Freeman >>>>>> －－－－－－－－－－－－－ >>>>>> Freeman(Yue) Fang >>>>>> >>>>>> Red Hat, Inc. >>>>>> FuseSource is now part of Red Hat >>>>>> Web: http://fusesource.com | http://www.redhat.com/ >>>>>> Twitter: freemanfang >>>>>> Blog: >>>>>> http://freemanfang.blogspot.**com<http://freemanfang.blogspot.com> >>>>>> >>>>>> http://blog.sina.com.cn/u/**1473905042<http://blog.sina.com.cn/u/1473905042> >>>>>> weibo: @Freeman小屋 >>>>>> >>>>>> On 2012-12-14, at 下午11:21, Bengt Rodehav wrote: >>>>>> >>>>>> Thanks for your reply Achim. >>>>>>> >>>>>>> However, I don't quite understand how this works - is this >>>>>>> described somewhere? Things that would be nice to understand are: >>>>>>> >>>>>>> - What role does the jettyconfig file has? >>>>>>> - What role does etc/jetty.xml has? Is it generated? >>>>>>> - How is the final jetty configuration built up? >>>>>>> - When do I have to use a fragment (as described on the wiki)? >>>>>>> >>>>>>> To top it off I also have my ownd etc/org.ops4j.pax.web.cfg file. >>>>>>> I'm not sure how it works together with the default configuration >>>>>>> in the feature. >>>>>>> >>>>>>> Just trying to get a grasp on this... >>>>>>> >>>>>>> /Bengt >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2012/12/14 Achim Nierbeck <[email protected] >>>>>>> <mailto:bcanhome@googlemail.**com <[email protected]>>> >>>>>>> >>>>>>> >>>>>>> Hi Bengt, >>>>>>> >>>>>>> since the Jetty.xml isn't the "lead" configuration for the >>>>>>> jetty file and since the jetty is started in the "embedded" >>>>>>> style you need to get a hold of this a bit different, or >>>>>>> you use a jetty-web.xml file. >>>>>>> >>>>>>> I'm not sure about the right syntax right now, but since it >>>>>>> doesn't work and the jetty.xml is interpreted after the >>>>>>> server >>>>>>> is configured you probably need some getAttribute first. >>>>>>> A maybe not so good matching example can be found at [1] >>>>>>> >>>>>>> regards, Achim >>>>>>> >>>>>>> [1] - http://nierbeck.de/cgi-bin/** >>>>>>> weblog_basic/index.php?p=165<http://nierbeck.de/cgi-bin/weblog_basic/index.php?p=165> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2012/12/14 Bengt Rodehav <[email protected] >>>>>>> <mailto:[email protected]>> >>>>>>> >>>>>>> >>>>>>> I'm running a web application on Karaf 2.2.8. I need to >>>>>>> send quite a lot of data to the server using the POST >>>>>>> method. I get the following error message on the web >>>>>>> browser side: >>>>>>> >>>>>>> Form too large1588889>200000 >>>>>>> >>>>>>> After googling I found how to reconfigure this on >>>>>>> http://wiki.eclipse.org/Jetty/** >>>>>>> Howto/Configure_Form_Size<http://wiki.eclipse.org/Jetty/Howto/Configure_Form_Size> >>>>>>> . >>>>>>> >>>>>>> I therefore modified the etc/jetty.xml as follows: >>>>>>> >>>>>>> ... >>>>>>> <Configure class="org.eclipse.jetty.**server.Server"> >>>>>>> <Call name="setAttribute"> >>>>>>> >>>>>>> <Arg>org.eclipse.jetty.server.** >>>>>>> Request.maxFormContentSize</**Arg> >>>>>>> <Arg>2000000</Arg> >>>>>>> </Call> >>>>>>> ... >>>>>>> >>>>>>> But I still get the same error message. The configuration >>>>>>> hasn't changed. Am I doing this the wrong way? >>>>>>> >>>>>>> /Bengt >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/** >>>>>>> display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/> >>>>>>> > >>>>>>> Committer & Project Lead >>>>>>> OPS4J Pax for Vaadin >>>>>>> >>>>>>> <http://team.ops4j.org/wiki/**display/PAXVAADIN/Home<http://team.ops4j.org/wiki/display/PAXVAADIN/Home>> >>>>>>> Commiter & >>>>>>> Project Lead >>>>>>> blog <http://notizblog.nierbeck.de/**> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> -- >>>>> Jean-Baptiste Onofré >>>>> [email protected] >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >>>>> >>>> >>>> >>> >>> >>> -- >>> >>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer >>> & Project Lead >>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> >>> Commiter & Project Lead >>> blog <http://notizblog.nierbeck.de/> >>> >> >> > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
