[Building Sakai] memory leaks

[Ron Peterson]

2010-08-07_21:58:51-0400 Hedrick Charles <hedrick at rutgers.edu>:
> We used Java 6 in 64-bit mode for a whole year with Sakai 2.6. I run with a 12 GB JVM. The limiting factor is the amount of time for a full GC (which doesn't happen often, but does happen). You''ll need to add -Dsun.lang.ClassLoader.allowArraySyntax=true  to the Java options.
> 
> Our main approach has been to use a lot of memory and just live with it for a couple of weeks.

I've been running Sakai on 32 bit linux for years.  I think I'll be
looking at moving to a 64 bit box I have sooner than later, so that I
can give my JVM some more headroom.

> We've just moved SSL processing to a load balancer. There's some reason to think that a lot of the leaks are in Tomcat's SSL code. We just moved from an old Barracuda to a Crescendo that can do 1/2 Gbps of SSL (and that's their low-end model).

I run Tomcat through Apache via ajp, so Tomcat SSL shouldn't be an
issue.

-Ron-

> On Aug 7, 2010, at 1:09:44 PM, Ron Peterson wrote:
> 
> > 2010-06-24_12:30:35-0400 Charles Hedrick <hedrick at rutgers.edu>:
> >> We currently have to restart Sakai every week or two because it keeps growing. There are obviously memory leaks.
> > 
> > I restart Sakai daily because of this.  It's been a persistent problem
> > as long as we've been using Sakai.  I use munin to capture the output of
> > tomcat's manager/status page, and the vm usage graph is a very
> > consistent sawtooth pattern which will crash the instance if I don't
> > restart.
> > 
> > I'm currently running on 32 bit linux, so my vm overhead is limited.
> > I'm in the process of migrating our instance to 64; but all I expect to
> > accomplish is to delay the inevitable.
> > 
> > This is not good.
> > 
> > I'm currently running 2.6.2.  What is the latest supported version of
> > both the java jdk and tomcat that is supported for my installation?
> > 
> > -Ron-
>