You should check if your "memory leak" is not actually the resource demands of 150 users outpacing the resource cleanup of the JVM garbage collector.
Try connecting jvisualvm.exe to the Tomcat instance and look at the memory usage graphs. Do you see consistent drops indicating the JVM garbage collector is at work? Or is it just a slowly rising plateau? The latter would indicate some kind of memory leak. The former would indicate more fine tuning of JVM options is required. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Java-memory-leak-tp5095257p5095322.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
