GWTTestCase: Forked JVM has been killed on time-out after 60 seconds

336 views
Skip to first unread message

dm3sol

unread,
Jul 29, 2009, 1:58:50 AM7/29/09
to Codehaus Mojo gwt-maven-plugin Users
I run my test with gwt-maven-plugin in maven2 ( Mac) and I get the
test killed after 60 seconds:

INFO] [gwt:test {execution: test}]
[INFO] using GWT jars from project dependencies : 1.6.4
[INFO] Unpack native libraries required to run GWT
[INFO] establishing classpath list (scope = test)
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running
biz.carboncreditcorp.greenprogram.web.gwt.client.GwtAppTest
killed.
[WARNING] Forked JVM has been killed on time-out after 60 seconds
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 minute 39 seconds
[INFO] Finished at: Tue Jul 28 22:50:03 PDT 2009
[INFO] Final Memory: 17M/30M
[INFO]
------------------------------------------------------------------------

Anyone has any idea what's going on?

Pablo

unread,
Jul 29, 2009, 6:21:57 AM7/29/09
to Codehaus Mojo gwt-maven-plugin Users
Hi,

Have you tried the following option?
http://mojo.codehaus.org/gwt-maven-plugin/test-mojo.html#testTimeOut

Cheers,
Pablo

dm3sol

unread,
Jul 29, 2009, 6:14:55 PM7/29/09
to Codehaus Mojo gwt-maven-plugin Users
Thanks Pablo,

yes I did, but with the same result:

[INFO] [gwt:test {execution: test}]
[INFO] using GWT jars from project dependencies : 1.6.4
[INFO] Unpack native libraries required to run GWT
[INFO] establishing classpath list (scope = test)
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running Test for a Seeders Grid
[INFO] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
71.431 sec <<< FAILURE!
[INFO] testPlantSimple
(biz.carboncreditcorp.greenprogram.web.gwt.client.GwtAppTest) Time
elapsed: 71.413 sec <<< ERROR!
[INFO] com.google.gwt.junit.client.TimeoutException: The browser did
not contact the server within 60000ms.
[INFO] - 1 client(s) haven't responded back to JUnitShell since the
start of the test.
[INFO] Actual time elapsed: 60.038 seconds.
[INFO] at com.google.gwt.junit.JUnitShell.notDone(JUnitShell.java:
551)
[INFO] at com.google.gwt.dev.HostedModeBase.pumpEventLoop
(HostedModeBase.java:556)
[INFO] at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:
652)
[INFO] at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:
346)
[INFO] at com.google.gwt.junit.client.GWTTestCase.runTest
(GWTTestCase.java:219)
[INFO] at junit.framework.TestCase.runBare(TestCase.java:134)
[INFO] at junit.framework.TestResult$1.protect(TestResult.java:110)
[INFO] at junit.framework.TestResult.runProtected(TestResult.java:
128)
[INFO] at junit.framework.TestResult.run(TestResult.java:113)
[INFO] at junit.framework.TestCase.run(TestCase.java:124)
[INFO] at com.google.gwt.junit.client.GWTTestCase.run
(GWTTestCase.java:132)
[INFO] at junit.framework.TestSuite.runTest(TestSuite.java:232)
[INFO] at junit.framework.TestSuite.run(TestSuite.java:227)
[INFO] at junit.framework.TestSuite.runTest(TestSuite.java:232)
[INFO] at junit.framework.TestSuite.run(TestSuite.java:227)
[INFO] at junit.framework.TestSuite.runTest(TestSuite.java:232)
[INFO] at junit.framework.TestSuite.run(TestSuite.java:227)
[INFO] at org.codehaus.mojo.gwt.test.MavenTestRunner.doRun
(MavenTestRunner.java:105)
[INFO] at junit.textui.TestRunner.start(TestRunner.java:180)
[INFO] at org.codehaus.mojo.gwt.test.MavenTestRunner.main
(MavenTestRunner.java:63)
[INFO]
[INFO]
[INFO] Results :
[INFO]
[INFO] Tests in error:
[INFO] testPlantSimple
(biz.carboncreditcorp.greenprogram.web.gwt.client.GwtAppTest)
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] There was test failures.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 minutes 19 seconds
[INFO] Finished at: Wed Jul 29 14:00:59 PDT 2009
[INFO] Final Memory: 19M/52M


Here is my pom.xml:

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.1</version>
<configuration>
<argLine>-XstartOnFirstThread -Xmx512M -Xss1024k</argLine>
<includes>**/GwtTestSuiteApp.java</includes>
<testTimeOut>1800</testTimeOut>
</configuration>
<executions>
<execution>
<id>test</id>
<goals>
<goal>test</goal>
</goals>
<phase>test</phase>
</execution>
</executions>
</plugin>

No idea what to do now. I use Junit4.4.

-- Dusan

On Jul 29, 3:21 am, Pablo <rug...@gmail.com> wrote:
> Hi,
>
> Have you tried the following option?http://mojo.codehaus.org/gwt-maven-plugin/test-mojo.html#testTimeOut

dm3sol

unread,
Aug 13, 2009, 8:38:04 PM8/13/09
to Codehaus Mojo gwt-maven-plugin Users
I've found the problem and this is just for those who would end up
trying to solve similar mysterious issue:

I've run the maven test with java 1.6 (windows, linux) and it worked
without any change. As a Mac dude, I can not run GWT hosted mode on
java 1.6 ( 64 bit) and therefore Gwt tests will not work either. So I
dived deeper in this issue. The thing that I could run it on windows
java 1.6 pointed me to the class loading. However, I could not found
anything wrong in the output except that I simply took an execution
command line from "mvn --debug -Dtest=MyGwtTest gwt:test" and try to
find out which library may cause this. Tidies work, but I found the
cause:

<dependency>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
version>2.8.1</version>
</dependency>

Once I removed it from my pom.xml, all Gwt tests run like a charm..
and faster too. The xerces library was left from previous
developments. Yes, bad me, I have to clean up while I am doing re-
engineering...

hope this helps somebody.. :-))

-- Dusan
Reply all
Reply to author
Forward
0 new messages