------art_594_17454976.1142454744155
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

JRuby currently uses Java threads to implement Ruby threads, and therefore
the only deadlock detection available is that provided by Java. However, if
you have threads deadlocking it is, as others have said, an issue with your
code that should be corrected. Ruby makes an assumption that the threads
will never wake up (or perhaps knows they will never wake up because of
circular dependencies) and chooses to kill them. In Java, you're perfectly
welcome to create deadlocked threads and Java will allow you to deadlock if
that's how you choose to write your code. Either way, if you have deadlocks,
you need to correct that in your code rather than expecting the interpreter
to save you.

On 3/11/06, Mc Osten <riko / despammed.com> wrote:
>
>
> So I can't assume JRuby (for example) will act the same, can I?
>
>


--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com

------art_594_17454976.1142454744155--