jdk 1.8.0_45 problems

[Bruce Schuchardt <bs...@pivotal.io>]

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.

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.

Re: jdk 1.8.0_45 problems

[William Markito <wm...@pivotal.io>]

Hi Bruce,

I've checked Jenkins and we are set to run with "latest 1.8" which
currently is 1.8.0_66 on ASF Jenkins.

Thanks!

On Wed, Nov 25, 2015 at 8:41 AM, Bruce Schuchardt <bs...@pivotal.io>
wrote:

> 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.
>
> 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.
>



-- 

William Markito Oliveira
-- For questions about Apache Geode, please write to
*dev@geode.incubator.apache.org
<de...@geode.incubator.apache.org>*