|
Hi, Usecase: |
Replies: 5 comments 3 replies
|
To make sure we're talking about the same details: different versions of Jetty (if this is a Jetty based Fuseki) have different settings.
|
|
Q: Which version of Fuseki? Q: How is the update requests sent? Content type application/sparql-update or as an HTML form? Q: Just how large is "large"? Q: What error are you getting in the log file? |
|
In Jetty12, it is only HTML forms that have size limits. Workaround for Fuseki 5.3.0: One way to set this is to use a Java system property: (this is 20Mbytes): For the fuseki-server script: If that is confirmed to work (I can't easily try it just at the moment), then this is a Fuseki bug to fix in 5.4.0. Another way is to send large requests, while still using |
|
I can recreate the situation. Issue #3110 fuseki-server.jar 5.2.0 works because it is a different architecture (it's a webapp/war file and server packed as one jar). 5.3.0 is a not webapp. I have tried a fix but Jetty is not picking up the increased HTML form size limit whether set using a system property or by API calls during server build. |
|
I'm afraid there isn't a workaround for 5.3.0. The Jetty system property setting will be overridden by Fuseki (it was setting the buffer size but only to 1Mbyte and this was fixed and overrides any settings). |
I'm afraid there isn't a workaround for 5.3.0. The Jetty system property setting will be overridden by Fuseki (it was setting the buffer size but only to 1Mbyte and this was fixed and overrides any settings).