You've not said where this template is, but is it pointed to by a CF mapping, using a UNC or mapped drive perhaps? If you don't use the "save classes" option, then CF will need to recompile the file and therefore need to access the source again.But at least the odds of it hitting But, when the server was hung, I can still be able to logon the cfide/administrator/index.cfm !
The SetupOk, so basically the system gets a "grading engine" to do some calculations based on given inputs. Nothing else is affected, only JRun. Changing "Chapter 3" to "My chapter III" and no change in the remaining chapters Is a "object constructor" a shorter name for a "function with name `object` returning type `object`"? Again, too much to explain here.BTW, one may wonder if this was related to an issue described here: http://www.talkingtree.com/blog/index.cfm/2006/2/2....
Please type your message and try again. Nathan Strutz @nathanstrutz My problem today is: 503 Remote CFC request timed out waiting to execute. about dozens of requests for the homepage. http://jscience.net/request-timed/network-request-timed-out.html The server specs: CPU: 2x Dual-Core Xeon RAM: 4GB ECC Registered OS: Windows Server 2003 CF: CF8 Enterprise, JRun configuration Web: IIS DB: None The only thing that I can think
While that might be a short term band-aid to the problem, in most cases this will simply delay the onset of the symptoms rather than truely solve the problem.To back up You may want to re-install the connector. You may want to consider increasing the number of active threads in the thread pool.at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) 1java.lang.RuntimeException: Request timed out waiting for an available thread to run. You may want to consider increasing the number of active threads in the thread pool.2at jrunx.scheduler.ThreadPool$Throttle.enter(ThreadPool.java:116)3at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:425)4at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)The helpful hint provided in the exception message suggests increasing the active thread
© 2017 jscience.net