Charles O Nutter wrote:
> I can appreciate your frustration.
> It's very possible that one of the Ruby libraries involved IS actually
> spinning up threads. For a long time we thought there was no threading
> going
> on during gem installs; then we found that goofy timeout library that
> spawns
> a thread for every 1024-byte read. It's possible that somewhere, for some
> reason, one of the libraries being invoked uses some of Ruby's
> "lightweight
> threads" to move the parsing process along.

There is still a bug that was introduced in 0.8.3 that occurs when Ruby
code is executed from different Java threads;
in short: dynamic vars initialized on one thread are not visible
initialized on another thread;
This trips me when I'm using EclipseShell, because I execute Ruby code
on Background threads (Eclipse Jobs), which are taken from a  Threadpool.

I'm trying to get to the root of this, but I'm not quite there yet; one
thing I see is that EvaluationStates seem to be Thread specific (thread
local?),
and this causes the self field in EvaluationState to be null, which
can't be right.


Stupid question: if I execute this:
a = 1;
from one Java Thread A, what should be the result when I execute
p a
on Java Thread B? 

murphee
-- Blog @ http://jroller.com/page/murphee Maintainer of EclipseShell @
http://eclipse-shell.sourceforge.net/



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel

Reply via email to