Deadlock and JConsole

Hello,

I am quite new to beanshell and just want to clarify something before I hunt
for bugs that possibly aren't there. Is it ok to use interp.eval() on an
interpreter that is being used by JConsole.

I do something like this:
JConsole console = new JConsole();
interp = new Interpreter(console);
new Thread(interp).start();
try {
    interp.eval("... some stuff here ...");
} catch (EvalError e) {
    e.printStackTrace();
}

My main thread is waiting at jj_scan_token, another thread at the same place
(possibly console startup code?) and a 3rd thread at
JConsole.BlockingPipedInputStream.read(). I have also seen it blocking at
Document.readLock().

Is my above code simply a bad idea, or is there something more to this, in
which case I can dig around more.

Thanks
-Ed



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn