On 18 jun 2014, at 04:05, David Holmes david.hol...@oracle.com wrote:
Hi Staffan
On 18/06/2014 4:30 AM, Staffan Larsen wrote:
This test launches four other VMs, thus taking a very long time to run with
-Xcomp. The real change here is to increase the timeout of the test, but I
have also
On 18 jun 2014, at 04:11, David Holmes david.hol...@oracle.com wrote:
On 18/06/2014 4:40 AM, Staffan Larsen wrote:
This change is still looking for a reviewer.
Looks okay. Though in general the error handling in that code still seems
somewhat lacking - there are places where exception
Erik,
How about using Process.destroyForcibly() as a means to terminate the process
instead of using files for signaling?
/Staffan
On 17 jun 2014, at 23:13, Erik Gahlin erik.gah...@oracle.com wrote:
Yes, very weird
Could have been that I needed the tools.jar in the child processes, or it
Didn't know about destroyForcibly(). I could try that.
Erik
Staffan Larsen skrev 18/06/14 09:26:
Erik,
How about using Process.destroyForcibly() as a means to terminate the
process instead of using files for signaling?
/Staffan
On 17 jun 2014, at 23:13, Erik Gahlin erik.gah...@oracle.com
This looks a lot better!
(Since we’re using fancy new features we could use streams to find the
connector instance)
AttachingConnector ac =
Bootstrap.virtualMachineManager().attachingConnectors()
.stream()
.filter(c - c.name().equals(com.sun.jdi.ProcessAttach))
