Thanks for the prompt response Gwyn.
Gwyn wrote: > > Would this be testing while running in DEVELOMENT mode? > Yes, I've always unit tested in development mode. Gwyn wrote: > > If so, switch to DEPLOYMENT mode - I'm not sure of the details, but in > that mode, there are various things in there that are there to help > with development and which, I think, won't always be cleaned up at the > end of a test. (Possibly due to JDK bugs related to not always closing > filehandles?) > Unfortunately, I get the same behaviour in deployment mode. Gwyn wrote: > > If not, then I guess it's down to a profiler & seeing if you can work > out what's being created & hanging around & why. If it still looks > like Wicket, then post more details. > I was scared you were gonna say that :-) At the risk of being annoying - can you point me in the right direction? I'm a recent arrival in java-land, coming from .NET-land, and am unfamiliar with the various java tools for profiling etc. Just a name or two (e.g. of an eclipse or maven plug-in) would be enough for me to sort it out. I'd really appreciate the steer. Severian. -- View this message in context: http://www.nabble.com/Wicket-1.3.0-beta2---OutOfMemoryError-tf4073994.html#a11580858 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
