[WARN] Lost communication with remote process ?

Skip to first unread message


Jan 24, 2017, 10:01:47 AM1/24/17
to GWT Users
Anybody any idea what to do with the following error:
I haven't seen this before, I see it since GWT 2.8. It occurs sometimes between permutation 15-16 and sometimes between 11-12 like the exception below.
However, it ends with success, strange, and the application does work.

I receive it when it's been build by Jenkins.
Any idea what it is and how to solve it ?

- Ed

[INFO]             Compiling permutation 10...
[INFO]          Compiling
[INFO]             Compiling permutation 11...
[INFO]       [WARN] Lost communication with remote process
[INFO] java.io.EOFException
[INFO] 	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
[INFO] 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
[INFO] 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
[INFO] 	at com.google.gwt.dev.ExternalPermutationWorkerFactory$ExternalPermutationWorker.compile(ExternalPermutationWorkerFactory.java:154)
[INFO] 	at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
[INFO] 	at java.lang.Thread.run(Thread.java:745)
[INFO]       Compiling permutation 12...
[INFO]          Compiling
[INFO]             Compiling permutation 13...
[INFO]       Compiling permutation 14...
[INFO]          Compiling
[INFO]             Compiling permutation 15...
[INFO]       Compiling permutation 16...
[INFO]          Compiling
[INFO]             Compiling permutation 17...
[INFO]       Compiling permutation 18...
[INFO]          Compiling
[INFO]             Compiling permutation 10...
[INFO]    Compile of permutations succeeded
[INFO]    Compilation succeeded -- 866.139s
[INFO] Linking into /home/develop/gwt/work/prod/total/plus
[INFO]    Link succeeded
[INFO]    Linking succeeded -- 14.454s

Thomas Broyer

Jan 24, 2017, 12:02:00 PM1/24/17
to GWT Users
A quick look at the code reveals that after the exception is logged, a TransientWorkerException is thrown, and a TransientWorkerException means that compilation on a given worker has failed and should be retried in another worker.
This explains why it works in the end.

Now as to why the external worker seemingly closed the connection, possibly an OufOfMemory.
You can enable debug logging to get the stdout and stderr of the forked JVM.
Then try playing with the gwt.jjs.javaArgs system properties to tune the forked JVM (memory if it's a memory issue).
Or you could possibly simply use fewer workers.

Ed Bras

Jan 24, 2017, 1:56:33 PM1/24/17
to google-we...@googlegroups.com
Thanks Thomas,
It probably has to do with OutOfMemory problems, but I thought I had it kind of solved.
After the upgrade to 2.8 I had to increase the max memory from 1.5 to 2G, else I keep getting out of memory problems :(
Currently I have, on a quad core: 

<extraJvmArgs>-Xms1G -Xmx2G -Xss1024k -Dgwt.persistentunitcache=false</extraJvmArgs>


However, I think the 2G might be too much too allocate on the server. I will play around with the settings, thanks.

- Ed

You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/zIYAvNMnGtU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsub...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Ed Bras

Jan 25, 2017, 5:12:00 PM1/25/17
to google-we...@googlegroups.com
I decreased the Max heap size to 1756MB and the builds seem to go fine currently.

To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
Reply all
Reply to author
0 new messages