What if you had an CFC instance that was doing a lot of data manipulation within a loop?  I have noticed in some pages here that do just that, that the CF Service just keeps grabbing and grabbing resources from the server until the entire page has completed running or until the server runs out of resources.  It seems like it should be able to be forced to release the resources via triggering the GC manually although that is not what I have observed.  I do something like this to trigger the GC:
 
objSystem = CreateObject( "java", "java.lang.System" );
objSystem.gc();

 
On 3/9/06, Barry Beattie <[EMAIL PROTECTED]> wrote:
1) why do you want to explicitly kill these CFC instances ? if they're
stored in a persistant scope (session, application, server**) I'd
understand, but if they're part of a request their references will be
destroyed when the page finishes loading and they'll be garbage
collected soon enough. trust in the Java GC


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org

Reply via email to