[+GWT] Tomer,
I haven't run into this problem myself yet with Jetty, but it doesn't surprise me that it's there. It might be worth opening an issue to bring this to the attention of the GWT team. There might be something they can do about the problem when running hosted mode, but I suspect not (although I stopped researching the issue when I found the cause, since it isn't a bug in my application and a simple restart fixes things). If someone opens an issue and posts a link back to this thread, I'd be happy to lend my star to it. - Isaac On Mon, Jul 6, 2009 at 10:18 AM, Tomer<[email protected]> wrote: > Well, I have a Jetty complaint... > GWT 1.6 causes PermGen errors after refreshing many times. > By the way, PermGen memory can be configured too, only not through > Xmx. > > On Nov 16 2008, 5:30 pm, "Isaac Truett" <[email protected]> wrote: >> This is a fairly common complaint for Tomcat instances, especially >> older versions, where lots of new classes are being introduced at run >> time. Basically, something in Tomcat doesn't let go of old class >> definitions. These old class definitions clog up the PermGen space >> after multiple webapp deployments (or hosted mode refreshes). >> >> I don't know of anything that GWT can or could have done about this, >> other then perhaps creating fewer classes. Switching to -noserver and >> using another app server could help. Or if -noserver gives you >> heartburn, you might be able to hack in a newer version of Tomcat into >> regular hosted mode. Lastly, I've heard that Jetty is being introduced >> as a hosted mode option in trunk. I am not aware of any Jetty PermGen >> complaints. >> >> - IsaacOn Sat, Nov 15, 2008 at 7:11 PM, Ian Bambury <[email protected]> >> wrote: >> > This is something I first asked about in version 1.1 in 2006. >> > If you use RequestBuilder (HTTPRequest back in 1,1) then after a while and >> > a >> > number of F5s to refresh the hosted mode, Java bombs out with a PermGen >> > space error. >> > It doesn't do any good to to increase the Xmx - all that happens is that it >> > takes longer to fail and longer to recover when you kill it. >> > I'f fairly sure its a GWT problem because I'm on a different computer, a >> > different OS, a different version of Eclipse and a different version of >> > Java, and it still happens. >> > Has anything happened in the past 2 years? >> > Ian >> >> >http://examples.roughian.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
