New topics: Your Pet, IOU, Baby IQ, The Poisons, Birther II, Games, Future Power

Trying out the documentation theme?

Skip to end of metadata
Go to start of metadata
In this set of pages on Investigating A Slow Confluence Installation - Version 3.3.1, I document the steps I took to try and identify slow running operations on my copy of Confluence 3.3.1. I recently added about 10K pages and labels for an EGW topical index, roughly doubling the number of pages (not not total size of content). This should account for the recent slowdowns and non-responsive Confluence that I have seen.

In this set of topics I discuss how I examined the database, stack dumps, dealt with Confluence hangs, logged bugs with the vendor, examined robot activity, and took other defensive measures to keep my copy of Confluence running.

Please let me know if these topics helped you run your copy of Conflunece. You can use the "Add comment" on any of these pages to let me know. Please include your email addres in your comment, I will keep a copy of your email so we can correspond about Confluence, but quickly remove it from the comment you place here.

One of the cooler tools that Atlassian has built in the last four years is the Hercules log analysis tool. I was always amazed four years ago when I would make a support request, and the technician woudl give me answers for the problem I was reporting, as well as make me aware of other issues I didn't even know were a problem. Now Atlassian has a tool called Hercules that analyzes Confluence logs automatically.

My support request about the rogue CPU hogging thread in Confluence was met with a response by a technician claiming out of memory issues were the cause of my problems. He noted several other things from the Hercules logs also. There was no response about the specific thread stack trace I was asking about. They were also happy I disabled the global usage plugin, which is known not to scale well. (I get a max of 10K hits a day, that doesn't seem like a lot to me, but tech support reflexively recommends getting rid of that plugin. So I already disabled it, and am still seeing performance problems.) So I logged a response, with some more logs from yesterdays 3:00pm restart, which are lacking in any out of memory errors.

I decided to use the Support Tools plugin again to let Hercules analyze my current logs since yesterdays restart. Here is it's output for my logs, I switch to richtext editor so that all the urls are saved when I cut and paste it (it would be nice if Hercules would include the excerpt from my logs for each case):

Hercules found 66 matches for known problems ( show all / show top 10 ) in the following log file: /home/confluence.bobsgear/data/logs/atlassian-confluence.log

cp atlassian-confluence.log ../../logscopy/atlassian-confluence.herc2010-09-13.log

cp ../../current/logs/catalina.out ../../logscopy/catalina.herc2010-09-13.out

I grabbed the catalina.out since maybe it's thread dumps will give some clues what was happening at the time of the above log entries.

I'll look at these in more detail later. The ones worrying about Oracle are almost definitely not applicable to my instance.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.