I've tried the Pezi's workaround, and I confirm, its works for us as well. To answer to Tom, in ours cases, we've always got 0 failcount.
1. we start the container with only 1 CPU, the JVM dies.
# A fatal error has been detected by the Java Runtime Environment:
# Internal Error (objectMonitor.cpp:1559), pid=1996, tid=140506417796864
# guarantee(_recursions == 0) failed: invariant
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# An error report file with more information is saved as:
# If you would like to submit a bug report, please visit:
Now, I stop the container, change the number of cpu to 2 (or more), start it and the JVM works flawless.
uid resource held maxheld barrier limit failcnt
kmemsize 18055460 23142400 9223372036854775807 9223372036854775807 0
privvmpages 60263 563969 1048576 1061076 0
physpages 88778 407884 0 9223372036854775807 0
vmguarpages 0 0 1048576 9223372036854775807 0
oomguarpages 14097 329674 1048576 9223372036854775807 0