Gerhardt wrote:That makes no sense at all based on what you say. Unless the VM that had been stable decided on its own to misbehave from one moment to the next - unlikely, pieces of software don't have emotions that can flare up.
The consensus solution seems to be an upgrade of the JVM
Gerhardt wrote:No idea what you mean by that statement. There are plenty of answers explaining why one might get that. There is NOT one answer.
I see a lot of people experiencing similar sigsegv errors but I don't see many "answered" threads.
There haven't been any changes to our application or middle tier recentlyDoesn't necessarily mean anything. If the server is experiencing different traffic then that can cause a different execution path which causes an error that previously have no impact to cause a crash.