Re: java core dump

2016-02-16 Thread Jonathan Leech
Yeah my fix didn't fix anything; was barking up the wrong tree. The toObject() was the right one I think hotspot just optimized out the intermediate calls. Going to try upgrading to 1.8 before downgrading to u79, will also look at the Phoenix source code with respect to concurrency issues.

Re: java core dump

2016-02-15 Thread Andrew Purtell
You might also consider moving back down to 7u79 > On Feb 15, 2016, at 10:35 AM, Jonathan Leech wrote: > > Has anyone else seen this? Happening under load in jdk 1.7.0_80 / phoenix > 4.5.2 - cloudera labs. Based on the source code, It seems the JVM is calling > the wrong

Re: java core dump

2016-02-15 Thread James Taylor
Thanks, Jonathan. I haven't seen this, but a patch would be much appreciated. James On Monday, February 15, 2016, Jonathan Leech wrote: > Has anyone else seen this? Happening under load in jdk 1.7.0_80 / phoenix > 4.5.2 - cloudera labs. Based on the source code, It

java core dump

2016-02-15 Thread Jonathan Leech
Has anyone else seen this? Happening under load in jdk 1.7.0_80 / phoenix 4.5.2 - cloudera labs. Based on the source code, It seems the JVM is calling the wrong toObject(), and then dumping. The correct toObject() method is a couple parent classes away with some generics and Sun / Oracle must have