On Monday, November 10, 2014 10:45:37 AM UTC+1, luca.masini wrote: > > Hi all, I just updated a project using GWT 2.6.1 with version 2.7.0. > > Everything seems to works client side (after adding some dummy property on > the gwt.xml), the problem is server side. > > I noticed that my WLS 12.1.1 stopped working after one deploy, so I > started digging and I've found that the new gwt-servlet.jar fill the > Permanent Generation memory. > > I tried expanding it up to 512MB, but it can resist one more deploy, so I > reverted to 2.6.1. > > I saw that the jar size is quite the same, 9.2 vs 9.4 MB, so the problem > must be inside the byte code. > > Any idea ? >
Hmm, there hasn't been much changes to GWT-RPC since 2.6.1: https://gwt.googlesource.com/gwt/+log/2.6.1..2.7.0-rc1/user/src/com/google/gwt/user/server/ https://gwt.googlesource.com/gwt/+log/2.6.1..2.7.0-rc1/user/src/com/google/gwt/user/client/rpc/ Other changes are the update of Guava from 15.0 to 16.0.1 and Closure (sourcemaps, used to deobfuscate stacktraces): https://gwt.googlesource.com/gwt/+log/2.6.1..2.7.0-rc1/servlet/build.xml Or maybe you're using other things than GWT-RPC? but there haven't been much changes there too I believe. Have you looked at the content of the perm gen space? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/73cf6b13-7324-4782-b18b-15c6a22672fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
