Dave Cramer wrote:
I'm not too keen on the term FENCED, since it, in the PL/Java case
will lead to poorer isolation. Multiple threads running in the same
JVM will be able to share data and a JVM crash will affect all
connected sessions.
When was the last time you saw a JVM crash ? These are very rare now.
I think that's somewhat dependent on what JVM you're using. For the
commercial ones, BEA, IBM, and Sun, i fully agree.
In any case if it does fail, it's a JVM bug and can happen to any code
running and take the server down if it is in process.
Crash is perhaps not the right word. My point concerned level of
isolation. Code that is badly written may have serious impact on other
threads in the same JVM. Let's say you cause an OutOfMemoryException or
an endless loop. The former will render the JVM completely useless and
the latter will cause low scheduling prio. If the same thing happens
using an in-process JVM, the problem is isolated to that one session.
Regards,
Thomas Hallgren
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
