Bug: OOM PermGen space during Kryo

[jamoore]

During testing, gretzky OOM'd with "PermGen? space" which is a seldom occurrence these days. The log file shows:

2013-05-30 13:03:16,367 DEBUG [                   loci.formats.Memoizer] (l.Server-5) loaded memo file: /OMERO/BioFormatsCache/OMERO/ManagedRepository/user-4_5/2013-05/30/10-44-32.064/.20110629-Spat-1_1.tif.bfmemo (5091492 bytes)
2013-05-30 13:03:16,367 DEBUG [                   loci.formats.Memoizer] (l.Server-5) start[1369915395579] time[788] tag[loci.formats.Memoizer.loadMemo]
2013-05-30 13:03:16,367 DEBUG [                   loci.formats.Memoizer] (l.Server-5) start[1369915395579] time[788] tag[loci.formats.Memoizer.setId]
2013-05-30 13:03:16,371 INFO  [                 org.perf4j.TimingLogger] (l.Server-5) start[1369915395548] time[822] tag[omero.call.exception]
2013-05-30 13:03:16,373 ERROR [        ome.services.util.ServiceHandler] (l.Server-5) java.lang.Error:  Wrapped Exception: (java.lang.OutOfMemoryError):
PermGen space
java.lang.OutOfMemoryError: PermGen space
        at java.lang.Class.getDeclaredConstructors0(Native Method) ~[na:1.5.0_22]
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) ~[na:1.5.0_22]
        at java.lang.Class.getConstructor0(Class.java:2671) ~[na:1.5.0_22]

Though this may be coincidental, the fact is that Kryo does do class loading magic which would likely use more of the perm gen space. If so, the default perm gen value may have to be bumped. If this continues to happen (i.e. if kryo is not built for being used in a long-running application), then something more fundamental will have to be done (i.e. dropping kryo).

[jamoore]

Note: likely gretzky was running a quite old JDK5 like howe is currently:

hudson@howe:~$ ls -al  /proc/19078/exe 
lrwxrwxrwx 1 hudson hudson 0 2013-05-30 14:44 /proc/19078/exe -> /home/hudson/hudson/tools/hudson.model.JDK/5_0_22/bin/java

All the jobs which use a JDK5 for compilation should likely be carefully checked to deploy with JDK6.

[jamoore]

Another full hang today but without an OOM. See logs in omero@gretzky:~/Josh. This time PG was locked, most likely by various deletes.

[jamoore]

Closing as we've not seen any more of this. Minimum JDK version is now 6+ on these branches, so this hopefully won't be seen again.