Deadlock has been detected running Cacao Unit Tests playing with JMXMP connexion. This test closes and recreate the connector. Sometimes the close operation hangs.
The bug has been reproduced on Solaris/i386, but is in generic Java code.

In one thread, the call to ClientSynchroMessageConnectionImpl.sendWithReturn() contains a block first synchronized on 'notiflock' then synchronized on 'statelock' inside checkState().
In a second thread, the call to ClientSynchroMessageConnectionImpl.close() contains a block synchronized on 'statelock' then synchronized on 'notiflock'.


In attachment is the stack trace in deadlock situation, involving "Thread-17" and "Job_Executor11".