You may want to provide more information than that. For example: - The software versions (Java, Tomcat, MySQL, Magnolia etc). - Memory (GC) configuration for tomcat. - Number of magnolia instances. - Monitoring output from vmstat and top.
60% memory consumption at reboot seems pretty high assuming that there is virtually no load. Seems like you have configured mysql pesrsistence for jackrabbit. Try using file based persistence as an alternative. If MySQL is also running on the same machine then it could be too overloaded depending upon the mysql settings. If your mysql connections are getting lost midway, that could possibly mean that the vm controller is trying to throttle resources or putting a cap on resource utilization for your virtual node. Check with your hosting provider if this is the case but try testing you application on a local dedicated server first. Setting "autoReconnect" may alleviate your problem temporarily, but the problem may continue to manifest in other ways. HTH. ________________________________ From: Julien S. <[email protected]> To: Magnolia User-List <[email protected]> Sent: Sat, August 21, 2010 7:45:00 PM Subject: [magnolia-user] Configuration of virtual server with low resources Hello, there is a severe resource problem with my productive system every few days. (look at this please: http://s2.imgimg.de/uploads/Ressourcen87bc957fJPG.jpg) The system totally freezes and can only be restarted with virtuozzo. Background information: - it is a virtual server system with 1 GB Memory - os : debian lenny - magnolia running with help of: apache2, tomcat, mysql (repository) After reboot, the memory consumption is okay (around 60 %), but after some days the java process (which starts tomcat) takes more and more memory. May it have something to do with this magnolia error? ---- ERROR org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager 19.08.2010 03:34:42 -- could not execute statement, reason: The last packet successfully received from the server was 46,239,001 milliseconds ago. The last packet sent successfully to the server was 46,239,001 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem., state/code: 08S01/0 [...] Communications link failure ---- Is "autoReconnect" neccessary for magnolia and mysql? Please help me to solve this problem. Thanks in advance Julien ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
