We are still using CF 4.0.1 due to an inability to get 4.5.1 to consistently
run on our SPARC Solaris 2.6 systems. While we are impatiently waiting
for help from support, we have been seeing a two part problem in CF 4.0.1.
First, we see the CF Scheduler after running a few days stop running.
Within another day or two (of doing things like stopping and restarting
ColdFusion, etc.) suddently ColdFusion no longer will run at all, reporting
a corrupt Registry. If at that point in time we recover the Registry
from a backup previous to when ColdFusion Scheduler quit working, the
Scheduler starts up again.
We are in need of tips, pointers, tools to analyze the Registry problem,
etc.
Any information you might be able provide to enable us to work out this
problem would be appreciated.
--
Never apply a Star Trek solution to a Babylon 5 problem.
Larry W. Virden <mailto:[EMAIL PROTECTED]> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
