| Re: Out of Memory - LINUX
Brian,
I'm not sure that I agree with the IBM tech. You're right that Linux (and most modern OS's) will utilize any free memory in order to cache filesystem activity. In fact, I've seen this as high as 12GB on a 16GB server. The point is, as soon as this memory is needed for another process, the OS will immediate release it. So if you're looking at memory utilization graphs, it's important to exclude the system cache, in order to get a true view.
Now - based on the error, it seems that someone tried to load up a large zip file into OTM (see below - highlighted). The out of memory issue is likely code related, rather than JVM heap memory, which is why the error showed up in the glog.app.log and not the console.log file. So - some component of OTM was trying to unzip this file and was unable to deal with the expanded size.
2008-04-21 10:14:55.730 0 Error Exception java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
I believe there is a limit in how large uploaded files can be in OTM, but don't remember the exact limit (5, 10 or 20MB - something like that). There is another servlet that allows larger uploads, but it doesn't kick of Agents and other workflow actions.
I would find out who was doing the upload and then try it again with a smaller file.
--Chris |