Hi,
As the the error happens deep inside the JVM code, it’s unlikely to be a bug on JRebel side, just that we cause the code to flow in a way that might be otherwise unexpected. If you can try out whether the error reproduces on the latest jdk8 version, it would help us immensely at narrowing down the problem.
I did try running weblogic on jdk8u66 however the error did not reproduce on my end.