In C and C++, programmers must explicitly provide the routine for reclaiming dynamically allocated memory. When memory is not reclaimed (because a programmer forgets to do so, or because of a logic error), this causes the so-called memory leak. In Java programming, when an object is no longer used in the program, the object is marked for garbage collection. When the garbage collector executes the memory of such object is reclaimed. Therefore, memory leak that are common in other languages like C and C++ are less likely to happen in Java.
We are using Gentran 5.2-1 for Unix. To resolve our memory leak issue, we do the Gentran command "stopserver" then "startserver".