On 2010-09-08, Xu, Larry wrote: > I met a trick problem "forked jvm exited abnormally".
> I ran the JUnit test case in ant and set the fork=yes for getting EMMA > report. This can happen for a number of reasons, the most likely is that an exception is thrown during your tests that terminate the VM - a good candidate is an OutOfMemoryException. It could also be a test invoking System.exit or any other reason that stops a Java VM. > When I set back the fork=no , it work well. Your forked VM may start with different memory settings than the one running Ant, for example. > Someone said it is fixed bug in Ant 1.7.1. It caused the multiple > version of Ant or JUnit. Later in your mail you say you are using Ant 1.8.1. > In Ant1.7.1 , it will give you a tips to said multiple version of Ant > or JUnit exist. I don't think this would cause the forked VM to crash. Does the forked VM really crash or is the message wrong? If it crashes, can you identify the reason in some way? Add a verbose formatter (like plain), make sure all output goes to Ant's logging system and to a file so you get as much of information as possible. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
