Blogging Roller

After Anthony moved FreeRoller over to the JavaLobby server, I was nervously watching the server and waiting for it to go down. Now that Roller is hosted on a big honkin' server running the latest Tomcat (4.1.24), I have nobody to blame but myself when the system slows to a crawl or crashes. Actually, Roller is built on a giant stack of open source software (Struts, Velocity, Castor, OSCache, etc.) so there is plenty of blame to go around, but I'm not the blaming type.

Unfortunately, I did not have to wait long for disappointment. Roller crashed on Saturday with an out-of-memory exception (too many cache entries in memory?), so I tweaked the OSCache settings to cache only to disk. On Sunday, Roller exhausted the Tomcat thread pool (too much OSCache disk I/O?) and crashed again. This morning, I confugured OSCache for disk and memory caching with a limit of 100 cache entries, and I have configured Tomcat for 256MB max memory. Things seem to be holding up well so far, but will FreeRoller make it through the night?