We see this exception too. We believe this is related to the jdk versions.
In our case, the exception only happens on heavy workload, and after we
upgrade the jdk version , it is gone.
Currently, we use jdk1.6_35. I suggest you to try this.
On Thu, May 30, 2013 at 11:07 AM, Yonghui Zhao <[EMAIL PROTECTED]>wrote: