« Roller and JRoller... | Main | Why I care so much... »

JRoller not out of the fire yet.

Monday morning traffic has proven that the JRoller performance troubles are not quite over yet. That slow query I mentioned earlier was not the only problem with Roller 0.9.9. We have been experiencing heavy load and have had to restart multiple times.

Update: we're working with Kirk Pepperdine of JavaPerformanceTuning.com to zero in on what looks like a very bad memory leak.

Comments:

Sorry to hear of your woes Dave. We went through some issues as well at Blog-City (which is Java based also) when we released our version 3; but there is light at the end of the tunnel. Feel free to contact me off list if you want to trade war stories! ;)

Posted by Alan Williamson on June 14, 2004 at 09:25 PM EDT #

JRoller has been down for a while now. Considering the nature of the security bug (ROL-403), I've been thinking, probably just as well ... :( Not sure if ROL-403 is an isolated case or has already been fixed, will have to see about it when JRoller comes up again.

Posted by lowem on June 15, 2004 at 08:30 AM EDT #

I disabled XML-RPC until the problem is fixed.

Posted by Dave Johnson on June 15, 2004 at 10:37 AM EDT #

I'm pretty sure I know what the problem is, but I'm working on a Unit Test first so I can prove to myself it's fixed. This unit test is proving very difficult to write as I want to keep it server-side (not hitting a running instance over the wire).

Posted by Lance on June 16, 2004 at 12:01 PM EDT #

Post a Comment:
  • HTML Syntax: NOT allowed

« Roller and JRoller... | Main | Why I care so much... »

Welcome

This is just one entry in the weblog Blogging Roller. You may want to visit the main page of the weblog

Related entries

Below are the most recent entries in the category Roller, some may be related to this entry.