This may not actually be related to River, but it's a very curious bug that happens in River code. I posted the detailed question here:
http://stackoverflow.com/questions/7502905/what-can-cause-illegalmonitorstateexception-from-inside-a-synchronized-block The short version is that we're getting IllegalMonitorStateException thrown from code that looks like this: synchronized (lock) { lock.wait(timeout); } Shouldn't be possible, right? The River code in question is here: http://svn.apache.org/viewvc/river/jtsk/trunk/src/com/sun/jini/jeri/internal/mux/Mux.java?view=markup#l222 Chris
