Recently I reimplemented a relatively complex application. In this reimplementation, I used (among other new components) WebWork.
The previous implementation was speedy, but at the cost of architecture. It consisted mainly of JSP (with embedded Java code) and additional Java classes communicating with a database through JDBC. The reimplementation proved architecturally way better. The new architecture consists of WebWork, SiteMesh and other application specific components. But now I've run into serious problems. The application seemed to work fine for a while at first, but now it's experiencing serious memory problems. Fatal ones. It's eating memory - in fact, all memory - which halts the application/server. I'm not sure if it's a leak, or if the new memory "roof" is just above what the server can provide. I'm not saying this is due to WebWork. I'm looking for advice in general, and what - if any - part WebWork could play in this. Does WebWork have any caches? (Prohibiting garbage collection of application specific objects, which in this case can contain large amounts of data) I tried various memory profilers, without success (all profilers failed/crashed sooner or later in the process and/or I couldn't use the profiling data). "java -Xrunhprof" worked, but I couldn't make much sense of it. I'm running Orion. Thanks for any advice.. Regards, Markus. -- Markus Holmberg [EMAIL PROTECTED] _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
