You can ask the JVM nicely to perhaps consider doing some garbage collection, which might maybe sorta destroy the object.
There's no guaratees though :) ----- Original Message ----- From: "Kinley Pon" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Sunday, November 25, 2001 9:47 AM Subject: Java and Coldfusion 4.5 using memory > A question for those java - Coldfusion experts: > > When an object is instantiated with the statement > > <cfset pointToThisObject=objectName.methodName()>, > > the 'pointToThisObject' contains only the pointer address to the > instantiated object in memory. > > It appears that Coldfusion is not releasing the memory space and leaving a > "vague" reference to the java object. Being that this may be the case, the > memory is strinking which is causing a 'java.lang.OutOfMemoryError' to > occur. The java memory space is strinking when multiple users (client > workstations) are using the application. > > Is there a way to destroy or release this memory space? I have tried <cfset > pointToThisObject = ""> but it only clears the pointer but not the memory > space. > > Also, would you know how to determine what the memory usage would be within > Coldfusion during the before and after an object is instantiated? > > Please help...I would hope that Coldfusion would be able to handle its own > garbage collection when referencing java objects. > > talk soon - Kinley > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
