into the console window and hit enter and it keeps working.
Rainer Hermanns wrote:
Yes, these were my expierences as well... Even with command line startup, the same problem appears.
While deploying without reloading I do not get any OutOfMemoryErrors.
Since I start tomcat with mx512m there shouldn't be an issue with to less memory right after startup.
Same problem appears with LifeCycleErrors, which only occur while being in reload mode.
--Rainer
Drew McAuliffe wrote:
One thing that isn't clear: are you using Tomcat context reloading via some sort of IDE? For example, are you using Eclipse with Sysdeo's Tomcat plugin? I found that if you are continuously reloading the web app context, rather than restarting Tomcat, eventually you run out of memory. That's true in both Tomcat 4.1.x and 5.0. It's some sort of memory leak in the reloading process. I don't see it as a major problem with Tomcat since that kind of reloading isn't recommended for production, but it's something to be aware about in development. If you are reloading rather than restarting, just treat Tomcat like Windows and restart several times a day.:)
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
