Karthik wrote:
The java batch process runs on a 2 CPU server which has about 8GB RAM. The heap size was set to 1 gig. Before running the process, the java virtual memory was showing around 600MB, and right after the FOP process started, the memory went all the way up to 1.3 gig and stayed there.
The memory allocated to the JVM by the OS is not a reliable indicator for Java memory leaks, JVM implementations tend to keep memory allocations (as does basically every program which is supposed to be used in general in a one-shot mode), A peak indicating that the whole allowed heap size has actually been allocated is not unusual for FOP while processing large input. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
