> -----Original Message----- > From: [email protected] [mailto:user-list- > [email protected]] On Behalf Of Jan Haderka > Sent: Friday, July 31, 2009 11:25 AM > To: Magnolia User-List > Subject: RE: [magnolia-user] CPU 100% > > > On Fri, 2009-07-31 at 10:53 +0200, Carla Di Santis wrote: > > Ok thank you, > > > > >I presume you verified that 100% CPU is occupied by > > >the Tomcat and not by anything else? > > > > Yes, the tomcat occupies 100% CPU > > What is the response time of the webapp while this goes on? Is it still > responsive or is it very slow?
It is very slow > > > > > > > > Also, did you had the issue before upgrading to 3.6.6, or does it > happen > > > only since? Do you use Data Module and DMS? Any scheduled tasks on > your > > > instance (or scheduled data imports in case of using Data module)? > > > > I use Data Module but not DMS. There is a scheduled task but it was > terminated before the recognition of the problem. > > Another question then. Are you using workflow? Is it possible you have > time triggered workflow tasks? > I'm using workflow, but I never used activation by date. > > Do you know a method to understand what sub-process is running on > tomcat (indexing process, scheduled task ...), occupying CPU? > > You can use one of the java or tomcat monitoring tools ... read more at > http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html > http://wiki.apache.org/tomcat/FAQ/Performance_and_Monitoring > http://www.lambdaprobe.org/d/index.htm Tank you :) > > > > > >Also, did you had the issue before upgrading to 3.6.6, or does it > happen > > >only since? > > I used only 3.6.6 until now... > > So it is clean 3.6.6 installation and issue happens on author instance > only (assuming then your public instance is running on another instance > of tomcat and possibly on another hw, right? right: another hw > It this a CE or EE instance? > It is a CE instance > > > > > Thank you for advices > > > > Carla > > > > > > -----Original Message----- > > From: [email protected] [mailto:user-list- > [email protected]] On Behalf Of Bert Leunis > > Sent: Friday, July 31, 2009 8:32 AM > > To: Magnolia User-List > > Subject: RE: [magnolia-user] CPU 100% > > > > Hello, > > > > We had a slightly similar case a couple of months ago. We upgraded a > clients app to magnolia from 3.5.4 to 3.5.9, together with some minor > lay-out changes in templates. Through a report of the servers cpu we > found out that since the upgrade that tomcat instance occupied the > system in the range between 80 and 100% cpu. Very strange was (but > luckily) that the response time of the webapp (and others that run on > the same machine) did not significantly drop. > > > > We are sure it was this tomcat instance running magnolia 3.5.9. We > thought long and hard about a possible cause, but could not come up > with one. We upgraded to 3.5.9 to be able to move to a 3.6 which would > solve some issues our client experienced. We did not go so far as to > start monitoring to find out which class was causing the trouble. Our > hope and guess was that with a new release the trouble would be over. > And it was. We're now on 3.6.6 and the cpu is normal again. > > > > Not much help for you to get a solution I'm afraid, but just an extra > story. Good luck. > > > > Regards, Bert > > > > -----Original Message----- > > From: [email protected] [mailto:user-list- > [email protected]] On Behalf Of Jan Haderka > > Sent: vrijdag 31 juli 2009 7:36 > > To: Magnolia User-List > > Subject: RE: [magnolia-user] CPU 100% > > > > > > On Thu, 2009-07-30 at 10:14 +0200, Carla Di Santis wrote: > > > It is the author instance, using mysql for the repositories and it > is the only app running in tomcat. The public instances don't have any > problems. > > > I didn't find any error in the tomcat log. The restart doesn't > solve the problem. The problem go away on its own after a long time > (about 1 day). > > > I saw some posts about corruption of indexes, could be something > like that? > > > > At this point it could be anything. :( > > It can certainly be related to the indexes as indexing is done in the > > background. OTOH indexing is triggered by saving modified (or new) > > content, so it is unlikely to occur without a cause. Also should the > > indexes be corrupted, you would see errors in the logs and you would > > also have issues with search (not finding expected nodes). Easy way > to > > verify is to shutdown, delete all "index" folders from all workspaces > > and restart. The indexing will be performed synchronously on startup. > > > > Another possible cause could be communication errors with the DB, but > > again you would see that in the log files (unless, it just gets slow, > > but not timeout). I presume you verified that 100% CPU is occupied by > > the Tomcat and not by anything else? If you have multicore/CPU > server, > > are all the cores/CPUs occupied or only the one? > > > > Also, did you had the issue before upgrading to 3.6.6, or does it > happen > > only since? Do you use Data Module and DMS? Any scheduled tasks on > your > > instance (or scheduled data imports in case of using Data module)? > > > > > > > > > > > -----Original Message----- > > > From: [email protected] [mailto:user-list- > [email protected]] On Behalf Of Jan Haderka > > > Sent: Thursday, July 30, 2009 7:58 AM > > > To: Magnolia User-List > > > Subject: Re: [magnolia-user] CPU 100% > > > > > > > > > Without providing more details on your configuration and symptoms > of the > > > issue it would be very difficult to help you. > > > Also try to describe a scenario in which it happened list time ... > is it > > > a public or author instance ... do you have other apps running in > > > tomcat ... is there anything in the logs ... if it becomes slow, > does it > > > go away on its own given enough time or is the restart only way to > "fix" > > > the issue? > > > > > > Jan > > > > > > On Wed, 2009-07-29 at 18:12 +0200, Carla Di Santis wrote: > > > > Hi, > > > > I have a problem with Magnolia 3.6.6. > > > > Sometimes Magnolia take 100% CPU and it becomes very slow, > without > > > > apparent reason. The problem remains for some hours, also if I > stop and > > > > start tomcat. > > > > Can you help me? > > > > Tanks > > > > Carla > > > > > > > > > > > > ---------------------------------------------------------------- > > > > For list details see > > > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > > > To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia- > cms.com> > > > > ---------------------------------------------------------------- > -- > Best regards, > > Jan Haderka > Magnolia International Ltd. > > Meet us at the Magnolia Conference > http:/www.magnolia-cms.com/conference > > Magnolia® - Simple Open Source Content Management > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- Carla ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
