My 1.6 Xwiki install has started eating all my CPU when I try to go to any "dynamic page" like Blogs or What's New. Regular static pages work fine. Eventually, tomcat times out the connection to the rendered page. I upgraded to 1.7 but the behavior is still the same.
Make sure you don't allow robots to browse the PDF exports, as the export process takes a lot of computation power. See
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Performances#HRobotstxt
(and in general read all the performance tips on that page).
This is an internal corporate wiki and it only blows up when I try to go to "dynamic pages" as I mentioned above. There are no robots involved in any way.
Attached is the Xwiki.log, which doesn't seem to have much other than an NPE which I doubt is the cause. Also included is a thread dump in the catalina.out.
Note that our mailing list does not accept attachments, and it is a bad practice to post large attachments to public mailing list. The best thing to do is to use a public text sharing tool, like http://pastebin.com/ or http://rafb.net/paste/
I would hardly consider an 8 K attachment to be "large". The thread dump alone is too big to really put on pastebin but nonetheless: Xwiki.log: http://terracotta.pastebin.com/m3733cc04 Catalina.out: http://terracotta.pastebin.com/m8eaf221 I think "TP-Processor12" looks pretty suspect here.
At the very least this could be a denial of service attack because I'm sure it must be because of some entry someone made.
Unlikely.
Well, the version of Xwiki hadn't changed, nor tomcat, nor java. One day it's been running for months without issue and the next it is eating CPU every time I try to look at What's New or Blogs. What should I be looking at besides users posting? I've opened XE-351 to track the issue. Thanks for the help, -Dave