I'm back on this today, I were finally too busy last week.
Ready to use cut and paste:
cffunction name=onApplicationEnd returnType=void
cfargument name=applicationScope required=true/
cfscript
arguments.applicationScope.tranferFactory.shutdown();
/cfscript
/cffunction
2009/11/23 Mark Mandel
Should that be 'transferFactory' ? ;)
Mark
2009/11/23 Aurélien DELEUSIÈRE adeleusi...@gmail.com
I'm back on this today, I were finally too busy last week.
Ready to use cut and paste:
cffunction name=onApplicationEnd returnType=void
cfargument name=applicationScope required=true/
cfscript
This would impact unit tests that instantiate Transfer as well,
right? For example, I have coldspring instantiate my Transfer
instance and I instantiate CS to run unit tests over and over and
over. I can see how a suite of tests could exhaust the memory
quickly.
How would you suggest handling
On Tue, Nov 24, 2009 at 7:52 AM, Brian G brian-goo...@vfive.com wrote:
This would impact unit tests that instantiate Transfer as well,
right? For example, I have coldspring instantiate my Transfer
instance and I instantiate CS to run unit tests over and over and
over. I can see how a
Thank you Mark. TransferFactory.shutdown() is working great.
- Gabriel
On Sun, Nov 22, 2009 at 2:25 PM, Mark Mandel mark.man...@gmail.com wrote:
Now that IS interesting!
Looks like I overlooked something with EHCache.
EHCache will need to be shutdown when the application stops:
Hi Mark,
A. Now that the cache can be shutdown, I've been able to create an
error where a page loads several transfer objects and in the middle of
that process, another page reinitializes the application which
recreates Transfer and therefore ehcache. When that happens, I get the
following error:
Specifically during my testing, the error was caused in file:
transfer\com\cache\provider\EHCacheProvider.cfc
Line 89: cfif NOT getEHCacheManager().cacheExists(arguments.class)
Line 121: if(NOT getEHCacheManager().cacheExists(arguments.class))
- Gabriel
On Mon, Nov 23, 2009 at 9:44 PM, Dorioo
The question be-gets itself - why are you re-initialising Transfer mid
thread?
Is this in a production environment?
Mark
On Tue, Nov 24, 2009 at 1:44 PM, Dorioo dor...@gmail.com wrote:
Hi Mark,
A. Now that the cache can be shutdown, I've been able to create an
error where a page loads
It's currently in development but it's meant to simulate deploying new
code to production. As part of the deploy interceptor in Coldbox, it
automatically reinitializes the application after deployment which
could possibly be mid-thread with real users on the site.
So my thinking was that the
