After a long time of testing, the problem appears to occur only if multiple (java-) processes access one jar file concurrently. I'm still not sure whether both are just reading or (which seems more probable) one of them tries to write something.
After a long time of testing, the problem appears to occur only if multiple (java-) processes access one jar file concurrently. I'm still not sure whether both are just reading or (which seems more probable) one of them tries to write something.