Ruben, The next time the case reproduces, please collect the core dump. At least you would be able to analyze it later.
It might be a VM issue (e.g. failing compilation), or it might be a concurrency issue (e.g. data race in the parser code), or something completely different. You might find [1] fun to read and you might like to follow step-by-step should you have a JVM stuck condition again :) PS. core dump might contain private keys, passwords, so be careful if sharing the dump with someone. PPS. It might be great to pull [2] somehow, however, the status of javacc maintenance is, well, very very sad. They barely maintain javacc, and PRs do not seem to be welcome, so having javacc-related issues is sad :( [1] https://medium.com/@vladimirsitniko/analyzing-a-stuck-hotspot-c2-compilation-85e0ca230744 [2] https://github.com/javacc/javacc/pull/153 Vladimir
