It looks like this issue is caused by a bug introduced with JDK 6u5.
Here is an eclipse bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=214092
Here is the bug on Sun's bug tracker: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6614100
A workaround for this is to exclude the method from being optimized by hotspot or to downgrade the JDK before 6u5, namely JDK 6u3.
It looks like this issue is caused by a bug introduced with JDK 6u5.
Here is an eclipse bug report: /bugs.eclipse. org/bugs/ show_bug. cgi?id= 214092
https:/
Here is the bug on Sun's bug tracker: bugs.sun. com/bugdatabase /view_bug. do?bug_ id=6614100
http://
A workaround for this is to exclude the method from being optimized by hotspot or to downgrade the JDK before 6u5, namely JDK 6u3.