Pierre, what are you trying to do? Does the INSERT contain some variables/do some pattern matching?
If not (e.g. it's INSERT DATA), then you might be better off using the Graph Store Protocol: https://jena.apache.org/documentation/fuseki2/soh.html#soh-sparql-http On Wed, Aug 7, 2019 at 9:49 AM Pierre Grenon <[email protected]> wrote: > > Thank you, Lorenz. > > I did as you suggest and made the changes indicated. > > Fuseki started and seems to have accepted the jetty config. But then when > trying to send the update the same error occurs and the limit seems > unmodified (I used <Arg>200000000</Arg>). > > Caused by: java.lang.IllegalStateException: Form too large: 100948991 > > 10000000 > at > org.eclipse.jetty.server.Request.extractFormParameters(Request.java:545) > at > org.eclipse.jetty.server.Request.extractContentParameters(Request.java:475) > at org.eclipse.jetty.server.Request.getParameters(Request.java:386) > ... 50 more > > Can it be that the config does not override some default set elsewhere in > Fuseki? > > I’ll try to figure if I’m not doing something else wrong… > > Many thanks, > Pierre > > For reference: > https://www.eclipse.org/jetty/documentation/current/configuring-form-size.html > > > > From: Lorenz Buehmann [mailto:[email protected]] > Sent: 07 August 2019 08:08 > To: [email protected] > Subject: Re: Sensible size limit for SPARQL update payload to Fuseki2? > > > > > <?xml version="1.0"?> > > <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" > > "http://www.eclipse.org/jetty/configure_9_3.dtd<http://www.eclipse.org/jetty/configure_9_3.dtd>"> > > > > <Configure id="Server" class="org.eclipse.jetty.server.Server"> > > <Call name="setAttribute"> > > <Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg> > > <Arg><Property name="jetty.maxFormContentSize" default="1000000"/></Arg> > > </Call></Configure> > > > > [2019-08-06 17:07:48] Server ERROR SPARQLServer: Failed to configure > > server: 0 > > java.lang.ArrayIndexOutOfBoundsException: 0 > > at > > org.apache.jena.fuseki.cmd.JettyFusekiWebapp.configServer(JettyFusekiWebapp.java:297) > > at > > org.apache.jena.fuseki.cmd.JettyFusekiWebapp.buildServerWebapp(JettyFusekiWebapp.java:243) > > at > > org.apache.jena.fuseki.cmd.JettyFusekiWebapp.<init>(http://JettyFusekiWebapp.java:99<http://JettyFusekiWebapp.java:99>) > > at > > org.apache.jena.fuseki.cmd.JettyFusekiWebapp.initializeServer(JettyFusekiWebapp.java:94) > > at org.apache.jena.fuseki.cmd.FusekiCmd.runFuseki(FusekiCmd.java:371) > > at > > org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec(FusekiCmd.java:356) > > at jena.cmd.CmdMain.mainMethod(CmdMain.java:93) > > at jena.cmd.CmdMain.mainRun(CmdMain.java:58) > > at jena.cmd.CmdMain.mainRun(CmdMain.java:45) > > at > > org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.innerMain(FusekiCmd.java:104) > > at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:67) > > > > So I suppose I need a complete jetty config file rather than a snippet > > (unless the above is erroneous anyway). I wasn't able to find the default > > jetty configuration file in the jars. > > > > I found this > > https://github.com/apache/jena/blob/master/jena-fuseki2/examples/fuseki-jetty-https.xml<https://github.com/apache/jena/blob/master/jena-fuseki2/examples/fuseki-jetty-https.xml> > > But it mentions needing configuring further things and I have no clue how > > to adapt it. > > if you don't need HTTPS resp. SSL, you can just remove everything that > configures the SSL stuff: > https://github.com/apache/jena/blob/master/jena-fuseki2/examples/fuseki-jetty-https.xml#L179-L285<https://github.com/apache/jena/blob/master/jena-fuseki2/examples/fuseki-jetty-https.xml#L179-L285> > > > And then add > > <Call name="setAttribute"> > <Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg> > <Arg>2000000</Arg> > </Call> > > with whatever size you need. > > And don't forget to change the port, in the file it's configured with > 8082 compared to default 3030. > > THIS E-MAIL MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION. > IF YOU ARE NOT THE INTENDED RECIPIENT (OR HAVE RECEIVED THIS E-MAIL > IN ERROR) PLEASE NOTIFY THE SENDER IMMEDIATELY AND DESTROY THIS > E-MAIL. ANY UNAUTHORISED COPYING, DISCLOSURE OR DISTRIBUTION OF THE > MATERIAL IN THIS E-MAIL IS STRICTLY FORBIDDEN. > > IN ACCORDANCE WITH MIFID II RULES ON INDUCEMENTS, THE FIRM'S EMPLOYEES > MAY ATTEND CORPORATE ACCESS EVENTS (DEFINED IN THE FCA HANDBOOK AS > "THE SERVICE OF ARRANGING OR BRINGING ABOUT CONTACT BETWEEN AN INVESTMENT > MANAGER AND AN ISSUER OR POTENTIAL ISSUER"). DURING SUCH MEETINGS, THE > FIRM'S EMPLOYEES MAY ON NO ACCOUNT BE IN RECEIPT OF INSIDE INFORMATION > (AS DESCRIBED IN ARTICLE 7 OF THE MARKET ABUSE REGULATION (EU) NO 596/2014). > (https://www.handbook.fca.org.uk/handbook/glossary/G3532m.html) > COMPANIES WHO DISCLOSE INSIDE INFORMATION ARE IN BREACH OF REGULATION > AND MUST IMMEDIATELY AND CLEARLY NOTIFY ALL ATTENDEES. FOR INFORMATION > ON THE FIRM'S POLICY IN RELATION TO ITS PARTICIPATION IN MARKET SOUNDINGS, > PLEASE SEE https://www.horizon-asset.co.uk/market-soundings/. > > HORIZON ASSET LLP IS AUTHORISED AND REGULATED > BY THE FINANCIAL CONDUCT AUTHORITY. > >
