What it seems like is that WAS is not able to remove running instance of Magnolia from memory when redeploying your webapp. Why is that, is hard to guess. My bet would be on repository not being shutdown properly and WAS just ignoring the problem and leaving it running on the background as zombie until all memory is wasted. If you want to know exactly what is hanging after redeploying your app you would need to do memory profiling. Now since you should not need to redeploy webapp on production several times it should still not be big deal there, specially if you are aware of the problem. Another thing you can do is to give your server more memory. BTW WLS (Weblogic) suffers from same problem and not only when redeploying magnolia. You can get same behavior with almost every bigger application that allocates local resources.
Since you are running your server from your IDE there might be even more things at play, but I think you should be able to configure it to fork the jvm for the server so all you need to do when the problem occurs is to kill the server only and not restart whole IDE. Jan On Tue, 2008-04-01 at 07:07 -0700, strutsAwhile wrote: > HI, > > I have installed magnoliaAuthor war on Websphere 6.1 (IRAD 7) and see > OutofMemory errors after republishing the project 3 or 4 times. The only way > is to shut down the IDE and restart again. Attached is a partial stacktrace. > The configuration is default and i'm pointing the repository to a local > filesystem path (c:xyz). Please let me know the solution for this, so that > it doesn't become an issue when i deploy on server > > Thanks, > Joseph http://www.nabble.com/file/p16418450/OutOfMemory.txt OutOfMemory.txt ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
