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. By the way: thanks for the ideas, guys. Even though this probably is not a River bug, you've stepped up to help. I appreciate it. Chris -----Original Message----- From: Sim IJskes - QCG [mailto:[email protected]] Sent: Thursday, September 22, 2011 3:20 AM To: [email protected] Subject: Re: What can cause IllegalMonitorStateException from inside a synchronized block? On 21-09-11 18:58, Christopher Dolan wrote: > That's a good thought, but I think it's the right stack. I have the > stacktrace in a screenshot, but not in text (sorry). It looks pretty > straightforward: > http://i.imgur.com/UPPQS.png > Chris > Stepping with a debugger can cause all kind of problems. Does it also occur in production? Gr. Sim -- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
