Hi magnolians! We are having many problems with our site. One of the problems is with a certain routine the following situation: The site does not work well in public and especially in the instance author, everything is very slow Generally, we do a restart tomcat, but when we try to kill the java process, he does not die, because he gets caught.
Usually it is to have only one java process running tomcat magnolia but when we checked, there are two and even three processes. all processes are locked and are difficult to kill. identified by analyzing the historical which is always the same time that the the java process will stop. Our support said it is not server problem, but the magnolia own application. well, i Checked the backup module and we dont have any backup set I checked too the Schedular modules. There are several schedular configured, but all this schedular run every 1 second. I think the scheduler is working well. There are similar cases reported on this problem? how to solve then? I brought the magnolia tomcat log when the error happens: [quote] INFO: Waiting for 1 instance(s) to be deallocated Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JBDC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memo ry leak, the JDBC Driver has been forcibly unregistered. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JBDC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the J DBC Driver has been forcibly unregistered. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-29] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-84] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-85] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-452] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-453] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-454] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-455] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-456] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-457] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-458] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-459] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Thread-460] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Transient File Reaper] but has failed to stop it. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [] created a ThreadLocal with key of type [org.apache.commons.lang.builder.ToStringStyle$1] (value [org.apache.commons.lang.builder.ToStringStyle$1@2e5f3d 46]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak. Jun 28, 2011 4:02:06 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [] created a ThreadLocal with key of type [org.apache.jackrabbit.name.NameFormat$1] (value [org.apache.jackrabbit.name.NameFormat$1@6eafd672]) and a value of type [java.util.regex.Matcher] (value [java.util.regex.Matcher[pattern=(([^ /:\[\]*'"|](?:[^/:\[\]*'"|]*[^ /:\[\]*'"|])?)?([^ /:\[\]*'"|](?:[^/:\[\]*'"|]*[^ /:\[\]*'"|])?) regi on=0,7 lastmatch=nt:base]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak [/quote] Imagine this situation, in time, the logrotate reboot the magnolia tomcat app and occurs this error. Perhaps you can help me? Sincerely, -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=51c0a28e-7256-408d-9577-4920ca664fae ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
