Thanks, Andy. I'll drop the jetty config attempt. (I surmise that the concern with bumping very high the form size would cause 'performance' issues.) I can somewhat toy with the jetty locally for testing but in any event it becomes tedious when working with remote servers deployed in varied ways. So, I'll keep the strategy client side.
With many thanks, Pierre 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. From: Andy Seaborne [mailto:[email protected]] Sent: 07 August 2019 09:45 To: [email protected] Subject: Re: Sensible size limit for SPARQL update payload to Fuseki2? Pierre, RDFLib/SPARQLWrapper is using an HTML form upload. The scalable way is to POST with "Content-type: application/sparql-update" and the INSERT in the body, then it will stream - directly reading the update from the HTTP input stream with no HTML Form (Request.extractFormParameters) on the execution path. Fro an HTML form, the entire requests ends up in memory - its the way that HTML forms have to handled to see all the name=value pairs in the form. Incidentally, the same is true in the client. The default form size is already bumped up to 10M from the Jetty default of 200K. If the server is running in verbose mode, the entire SPARQL update is read in for logging/debugging purposes. The default jetty configuration is in code. For the form size, that is JettyFusekiWebapp.createWebApp which is 10M - we can make that default bigger but not 101M which is the request. Otherwise, break the request into parts and send multiple requests. Andy On 07/08/2019 08:49, Pierre Grenon 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
