arne-bdt commented on issue #2787: URL: https://github.com/apache/jena/issues/2787#issuecomment-2440195519
I have my experience with threading and I like challenges. So I jumped on this bug, which could also be relevant for some of my work projects. But now I am at a loss. **Restoring the early return from JenaSystem.init() as implemented prior to [commit 8654c07](https://github.com/apache/jena/commit/8654c07f23a892c03a7367981d814c3c8b094f62) does not solve the deadlock bug.** It only reduces the time-window and thus the likelihood of an occurrence. The developed tests clearly show that the problem persists. So here we are again with two options: 1. Resolve the circular depencencies. Unfortunately I could not wrap my head around that yet and would be delighted if someone with more knowledge about cross-dependencies and the history of static Jena initialisers would take a look at it. 2. Force JenaSystem.init() to be called from a single-treaded context. (but that option has already been discarded out as last resort) -- 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]
