To close this out, I have validated that the IBM "unSafe" core dump issue was resolved in SR12 and, presumably, later releases.
"[email protected]" <[email protected]> wrote: >Thanks Esteban, > >That definitely looks to be the culprit? Time to file the paperwork >for a JRE patch, yay. :) > >sun_misc_Unsafe_get long__Ljava_lang_Object_2J+0x41 (0x00002B26C8251629 >[libjclscar_24.so+0x4d629]) > >Esteban Gutierrez <[email protected]> wrote: > >>Hi Jess/Ted, >> >>the SR11 release fixed a bug with their implementation of the >>sun.misc.unsafe.Get* methods in older IBM JDKs: >> >>http://www-01.ibm.com/support/docview.wss?uid=swg1IV12627 >> >>I know there are few other bugs related to the the sun.misc.unsafe >but >>it >>would be helpful to know the full stack backtrace. >> >>esteban. >> >> >> >> >> >>-- >>Cloudera, Inc. >> >> >> >>On Tue, Nov 12, 2013 at 7:50 PM, <[email protected]> wrote: >> >>> >>> >Interesting, it seems that you are the first user who is trying >>HBase >>> (0.94.7) on IBM JRE. >>> >>> Probably. >>> >>> >Which version of IBM JRE are you using? Unsafe MUST be supported by >>IBM >>> JRE in Java 6. >>> >>> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 >>> jvmxa6460sr12-20121024_126067 (JIT enabled, AOT enabled) >>> J9VM - 20121024_126067 >>> JIT - r9_20120914_26057 >>> GC - 20120928_AA) >>> JCL - 20121014_01 >>> >>> > >-- >Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
