Solution to the problem of memory overflow caused by Java Proxy in Domino

Environment: DOMINO6.02 Host: as400-820
I wrote a proxy in Java, compiling and running all normal. However, after the agent has run hundreds of times, it will complain: Java.lang.OutOfMemoryError, it is estimated that memory overflow error. The memory has been cleaned up in my program, and the code is as follows:
Sysdoc.recycle ();
Sysview.recycle ();
View.recycle ();
Doc.recycle ();
Db.recycle ();
System.GC ();
I ask you master, this is what reason. Is Domino's Java Virtual machine problem or Domino's setup problem?
---------------------------------------------------------------
　
Oh, last year I asked this question, one of my Java agent, the cycle run thousands of times, this error, has not been resolved. Personally, it's a domino JVM problem.
---------------------------------------------------------------
　
Memory leak a Java Virtual machine's garbage collection started too slowly, it is recommended that you put the Java Virtual machine initial allocation to save
Turn it up. If you have enough memory, you should be fine. Domino can only use 4GB of memory hehe
　
On this issue I have consulted the AS400 engineer of Tsinghua Violet, he said that may be Domino's JVM has a problem, suggested I go to play patches, alas, but where to find the patch ....
　
Another question bug0303 (patch) brother, you this question is on the PC or in 400 encountered.
　
After consultation, the following mitigation methods are obtained:
　
In the server's Notes.ini file, you can add one parameter:
javamaxheapsize=< bytes >
The specific values of this parameter should be based on the server's hardware environment and the actual needs of the application to adjust, the default value should be 64M, you can according to the situation appropriate to the major. For example, "javamaxheapsize=268435456" sets this value to 256MB.
Note After you add or modify this parameter, you should restart the Domino server.
　
If there is no better way, this paste will be stuck.
　
After testing, adding JVM caching does not solve the problem, and IBM engineers acknowledge that this is a problem with Domino's JVM.
　
In this way, I have used LS to rewrite this section of Java, to achieve the same function.