Re: Facing Challenges with WebSphere Portal 220.127.116.11
Unfortunately, we wouldn't be able to tell what the memory leakage is until a actual OutOfMemory or failure occurs producing a javacore or heapdump.
We can then process the heapdump for leak suspects.
For latest fixes for 6.1.02, please see link below.
PK80970 is the only one I see that may be applicable but you should look through them and the exceptions in the log.