I've been experiencing some OOM issues in a couple applications ever since I upgraded from 4.0.x to 4.1.x. I didn't change any code for the most part, just some descriptors and such. Has anyone else noticed memory-hogging issues with 4.1.x?
Even stranger, if I start up my app using "mvn jetty:run", browse a couple pages and hit Ctrl+C, it doesn't kill the process. I have to forcefully kill the process in order to shut down Jetty. This doesn't happen with the other web frameworks I'm using, so I'm confident it's caused by Tapestry 4.1.2. Thanks, Matt -- View this message in context: http://www.nabble.com/Memory-issues-with-Tapestry-4.1.x-tf4387514.html#a12508911 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
