We also noticed an abnormally high number of SEGVs and other JVM crashes. Release notes for later 1.8 builds note that some SEGV problems have been fixed.
If our Jenkins builds are using 1.8.0_45 we should move them to 1.8.0_66.
During development on feature/GEODE-77 we noticed bad behavior in jdk
1.8.0_45. Frequently a JVM would go dark for up to a minute and be
kicked out of the distributed system. Statistics records showed no GC
activity, typically showing up as a big spike in GC duration after a
period of no statistics being recorded. Host system load-averages
weren't that high, either.
- jdk 1.8.0_45 problems Bruce Schuchardt
- Re: jdk 1.8.0_45 problems William Markito
