admin@glassfish.java.net

Admin DevTests Improvements

From: Byron Nevins <byron.nevins_at_oracle.com>
Date: Fri, 15 Apr 2011 21:12:05 -0700

By popular request, I've implemented a platform-independent[1] way of
killing JVM processes. I added the method into GF code itself.

com.sun.enterprise.universal.process.ProcessUtils.killJvm(String
mainClassName)

I've added a tiny class to the devtests that is always run before
everything else. It will kill any JVMs that have either of these as the
main class:

ASMain
DerbyControl

-- Now you don't have to go through the annoying manual step of killing
processes when you kill the tests before they complete.

[1] sort of. I need to call native code to do the actual killing. As
far as the caller is concerned -- it runs everywhere.
-- 
Oracle <http://www.oracle.com>
Byron Nevins | Principal MTS
Phone: +1 6503958992 <tel:+1%206503958992>
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment