Sunday, August 14, 2016

Re: GWT 2.8.0 RC2 is here!

Okay and Tnx for the DOCTYPE  answers.

Now something else...

ECLIPSE RELOAD GWT WEB SERVER - MEMORY NOT CLEARED.

With RC1, it was impossible to reload the web server using the eclipse plugin.
With RC2, it is possible again.
However, there is a major problem encountered during the reload: the memory used by the previous web server has not been cleared, and the 2 web server occurences 
seem to share a unique adress space (coexisting threads?). In our case, the second web server is then unable to load its normal working content....

I am unable to assume about the problem origin: GWT plugin ? Eclipse (neon) config ? Jetty config ? Would this be a GWT bug to be filled?

Anyway, this problem was not present with 2.7.

Below is part of the eclipse console trace, containing a load part and a reload part... Observe the lines reporting memory percentage (the server was launched with -Xmx2000m).

Hope it helps.

Best regards to all.

Fil.



Running CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 1.8, -bindAddress, 127.0.0.1, -launcherDir, /home/pge/javaNB4projects/gwtPBP/war, -logLevel, INFO, -style, OBFUSCATED, mscp.gwt.pbp.GwtPBP]
Super Dev Mode starting up
   workDir: /tmp/gwt-codeserver-4597875986963250914.tmp
2016-08-13 15:56:24.325:INFO::main: Logging initialized @3463ms
   Loading Java files in mscp.gwt.pbp.GwtPBP.
   Ignored 2 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
   Module setup completed in 4879 ms
2016-08-13 15:56:27.534:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
2016-08-13 15:56:28.156:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@9c251b{/,null,AVAILABLE}
2016-08-13 15:56:28.172:INFO:oejs.ServerConnector:main: Started ServerConnector@1851946{HTTP/1.1}{127.0.0.1:9876}
2016-08-13 15:56:28.173:INFO:oejs.Server:main: Started @7311ms

The code server is ready at http://127.0.0.1:9876/
Code server started in 5.866 s ms
2016-08-13 15:56:28.352:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
INFO[3:56:30][S]PolyTED/

INFO[3:56:30][S]PolyTED/ContextInitialize... PolyTED V=11a
INFO[3:56:30][S]PolyTED/User init
INFO[3:56:30][S]PolyTED/User init done: 25 users 20 companies
INFO[3:56:30][S]PolyTED/initData start on server MMM DVP=true
INFO[3:56:30][S]PolyTED/initData 1003 nodes 244 attribs 2011 nuts 9454 cpv
INFO[3:56:30][S]PolyTED/Docu file loaded (dat) 508
INFO[3:56:30][S]PolyTED/Docu file loaded (typ) from ? to ?
INFO[3:56:31][S]PolyTED/Docu file loaded (lng) 975413
INFO[3:56:31][S]PolyTED/Docu file loaded (lnk) 255427/355692
INFO[3:56:32][S]PolyTED/Memory [11%M] after docuFile.reload()

INFO[4:05:06][S]PolyTED/Tracing started in /media/Shared/webApp/db/PBP/trace/trace.dvp.MMM.13.8

[...]

Reloading web app to reflect changes in /home/pge/javaNB4projects/gwtPBP/war
2016-08-13 19:23:40.167:INFO:oejs.ServerConnector:Thread-1: Stopped ServerConnector@1d0cfd6{HTTP/1.1}{127.0.0.1:8888}
INFO[7:23:40][S]PolyTED/ContextDestroy... 
INFO[7:23:40][S]PolyTED/ContextDestroyed
INFO[7:23:40][S]PolyTED/DataControl: thread exit
2016-08-13 19:23:40.180:INFO:oejsh.ContextHandler:Thread-1: Stopped c.g.g.d.s.j.WebAppContextWithReload@135ff34{/,file:/home/pge/javaNB4projects/gwtPBP/war/,UNAVAILABLE}{/home/pge/javaNB4projects/gwtPBP/war}
2016-08-13 19:23:40.185:INFO:oejs.Server:Thread-1: jetty-9.2.z-SNAPSHOT
INFO[7:23:42][S]PolyTED/

INFO[7:23:42][S]PolyTED/ContextInitialize... PolyTED V=11a
INFO[7:23:42][S]PolyTED/User init
INFO[7:23:42][S]PolyTED/User init done: 25 users 20 companies
INFO[7:23:42][S]PolyTED/initData start on server MMM DVP=true
INFO[7:23:42][S]PolyTED/initData 1003 nodes 244 attribs 2011 nuts 9454 cpv
INFO[7:23:42][S]PolyTED/Docu file loaded (dat) 508
INFO[7:23:52][S]PolyTED/Docu file loaded (typ) from ? to ?
INFO[7:23:52][S]PolyTED/Docu file loaded (lng) 975413
INFO[7:23:52][S]PolyTED/Docu file loaded (lnk) 255427/355692
INFO[7:24:00][S]PolyTED/Memory [74%M] after docuFile.reload()

Le vendredi 12 août 2016 03:25:18 UTC+2, Daniel Kurka a écrit :
Hi all,

I just build the GWT 2.8.0 RC2 and pushed it to maven central. The complete SDK is also available from here.

Please start testing and let us know if you run into any trouble and file bugs.

We are planing to release this as GWT 2.8.0 if we do not here about any serious issues within the next two weeks. The release notes for RC2 will be made available shortly after this notice, in the mean time you can take a look at the github repository.

Daniel,
on behalf of the GWT team

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.

No comments:

Post a Comment