Hi all,
We've had a persistent problem with the java executable not quitting (sometimes for hours) after running sutdown.bat. We have a memory leak with java's RAM usage rising steadily towards the 1.1Gb level and are required to restart every couple of days in order to regain performance when Jahia slows down or freezes. Unfortunately we do not always have the luxury of hours to wait for java to exit and so often need to force the application to quit. Experience has shown that this sort of shutdown may well be responsible for corruption in the Jahia database. Many times we restart to find that a container from one page is suddenly appearing on another page - in some cases the homepage! Does anyone have any knowledge of this or suggestions how to overcome it? My only idea at the moment is to monitor RAM usage and restart Jahia at an earlier stage when problems are less likely to occur. Kind regards, Paul ____________________________________________________________________________ This e-mail is intended for the use of the addressed recipient(s) only and may contain confidential and privileged information. If you have received this message in error, please delete the message and any attachments and copies immediately; and notify the sender by return e-mail. Any views expressed in this message or any attachments are those of the individual sender and do not necessarily represent the corporate opinion of the Catholic Education Office (CEO), Sydney. The CEO Privacy Policy is located at http://www.ceo.syd.catholic.edu.au ____________________________________________________________________________
_______________________________________________ install_list mailing list [email protected] http://lists.jahia.org/cgi-bin/mailman/listinfo/install_list
