On 03/07/2023 14:20, Dave Reynolds wrote:
We have a very strange problem with recent fuseki versions when running
(in docker containers) on small machines. Suspect a jetty issue but it's
not clear.
From the threads here, it does seem to be Jetty related.
I haven't managed to reproduce the situation on my machine in any sort
of predictable way where I can look at what's going on.
For Jena5, there will be a switch to a Jetty to use uses jakarta.*
packages. That's no more than a rename of imports. The migration
EE8->EE9 is only repackaging. That's Jetty10->Jetty11.
There is now Jetty12. It is a major re-architecture of Jetty including
it's network handling for better HTTP/2 and HTTP/3.
If there has been some behaviour of Jetty involved in the memory growth,
it is quite unlikely to carried over to Jetty12.
Jetty12 is not a simple switch of artifacts for Fuseki. APIs have
changed but it's a step that going to be needed sometime.
If it does not turn out that Fuseki needs a major re-architecture, I
think that Jena5 should be based on Jetty12. So far, it looks doable.
Andy
