Tomcat 5.5 and 6 and it works a few times -- I would say 6 or 7 before I
have to bounce the server to reclaim memory leaked during the reload.
If I reload magnolia at all during the day, I schedule a bounce the next
morning when load is lowest as preventative maintenance.
For the record, my repository is in MySQL so the memory footprint is
smaller than if I was using Derby for example and that buys me some
breathing room. The other webapps are relatively small home grown
webapps mainly for custom form processing or database searching. Some
of these other webapps were coded to work as a very rudimentary portlets
(sorry, nothing that conforms to the portlet spec) in magnolia pages.
The advice I posted regarding storing the <Context ... /> xml fragment
in a file outside server.xml still holds as best practice though.
--David
Grégory Joseph wrote:
Hi David,
Either 1 or 2 above allows you to stop, unload, make alterations,
whatever to a specific webapp without having to bounce the tomcat
server and disrupting any/all the other webapps running on that
tomcat instance. Just go into the manager webapp, stop the webapp,
make any alterations you need -- update jars, etc., ... and then
start the webapp again in the manager webapp.
This has inevitably lead to out of memory exceptions when restarting
an apps and taking the whole server down. Not fun. Which version of
Tomcat are you using? Have you been able to restart Magnolia instances
this way, with other apps running (say, *for example*, jira and
confluence? :D)
cheers,
-g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
