afs commented on issue #2755: URL: https://github.com/apache/jena/issues/2755#issuecomment-2456565771
Hi @SamuelBoerlin, Thanks for investigating. In the 5.1.0 logs, the error is on a read operation and the exception is happening after the query response has been sent so I don't think that 5.2.0 would be causing any visible dropped queries in the client. Is this the case? In the log sample from 5.1.0, there isn't any overlapping operations, query or update. The log shows that all queries and updates execute in sequence with no overlaps of operations. The last update was 15 HTTP requests back. Is the client software making calls from just one client thread/process or from several? What library is the client software running to send SPARQL requests? As updates are showing as happening, there isn't some old update starting before the log sample still hanging around. So I don't think data has been dropped. If that analysis is right, It is beginning to look like a thread-variable-consistency problem with the read-path. Jetty is probably using multiple threads causing true parallelism in the system, which is fine. In 5.2.0, the internal state is likely to be self-correcting, overwritten by a later read operation but that is speculation on my part. I may be able to reproduce something now. If you have cleaned up the config.ttl file, could you put the current one you are using on the issue so I have exactly the same as you? -- 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]
