|
From: Eyal Bar-I. <ey...@gm...> - 2006-04-07 07:00:46
|
Jim, It could be a Full GC that takes too long use the "-verbose:gc" flag to see if it happnes when you have a Full GC Eyal On 4/6/06, Jim Redman <jr...@er...> wrote: > > We have a graphical application that we run as an .exe using the > wrapper. It restarts on a timeout: > > ERROR | wrapper | 2006/04/07 00:08:05 | JVM appears hung: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2006/04/07 00:08:05 | JVM did not exit on request, > terminated > > I don't really case about the wrapper timeout, the application is > interactive and the user can take care of real problems, but I'm > wondering what we're doing that's causing a problem. > > Are the "pings" sent from the Java Event thread? The application > could use a little optimization and is a memory hog. We tend to go into > phases in the program where we'll take 100% CPU time, such as compiling > applications, so we get, eg this: > > INFO | wrapper | 2006/04/06 23:32:15 | Wrapper Process has not > received any CPU time for 141 seconds. Extending timeouts. > > but even during this the screen is repainting (usually and slowly). > > Not too important, but any thoughts appreciated. > > Jim > > -- > Jim Redman > (505) 662 5156 x85 > http://www.ergotech.com > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |