On 22-09-11 14:04, Christopher Dolan wrote:
It's quite reproducible, but only in integration not in isolation
(yet). It was discovered as a hang in QA, then after several
reproductions, someone attached a debugger and found that surprising
exception.
We've discovered that switching from Sun Java 1.6 back to 1.5 makes
it go away.
One noteworthy fact I've since learned (and it's obvious from the
stacktrace in retrospect): this is a C++ thread and the root of the
Java stack comes from C++ via JNI. In theory that shouldn't matter,
right? But that's sure has a suspicious smell to me.
I guess the exception is created JNI side.
You could look in the jdk sources if there are other causes for the
exception. Maybe the underlying implementation or OS calls produce
unexpected returns.
Your are sure you have no JNI code loaded elsewhere? Maybe there is some
other native code corrupting the heap or stack?
You could also look if it is not an InterruptedException in disguise.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
