afs commented on issue #3837: URL: https://github.com/apache/jena/issues/3837#issuecomment-4231265796
Quick update: I ran the script and got the server to deadlock sometimes. One log ends: ``` ... [2026-04-12 10:35:04] Fuseki INFO [8250] 200 OK (12 ms) [2026-04-12 10:35:04] Fuseki INFO [6250] 200 OK (32.827 s) ``` so that is 2000 request apart and taking 33 seconds. 2 others logs also have an exactly 2000 gap. Fuseki configures Jetty with max (and default) 20 threads. This has been the Fuseki setting for a long time. Setting it to 200 threads, which is Jetty's default, and no lockup and it seems to finish quickly (>14,000 requests) but the log ends with ``` ... [2026-04-12 11:02:10] Fuseki INFO [14210] 200 OK (23 ms) [2026-04-12 11:02:10] Fuseki INFO [14208] 200 OK (21 ms) [2026-04-12 11:02:10] Fuseki INFO [14217] 200 OK (23 ms) [2026-04-12 11:02:10] Fuseki INFO [2256] 404 Not Found (13.613 s) [2026-04-12 11:02:10] Fuseki INFO [2365] 404 Not Found (13.444 s) [2026-04-12 11:02:10] Fuseki INFO [2514] 404 Not Found (13.213 s) [2026-04-12 11:02:10] Fuseki INFO [2010] 404 Not Found (14.339 s) ... ``` The number of connections (`netstat -t`) climbs to, say 330, and then drops ~100 so that's the kernel clearing up connections. My machine has about 30 other connections. When it deadlocks, CPU isn't too high so unlikely to be a major GC close to max RAM. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
