Any ideas about what could be crashing CF 10 standard repeatedly? My box is a virtualized Windows Server 64bit 2008 R2, Apache 2.2, 8GB RAM.
I've tried increasing the JVM memory settings, using the latest JVM externally, cleaning up code and slower queries, and rebuilding the web connector. Restarting the CF service fixes things until the next crash. When CF is unresponsive, Apache is serving static pages just fine; FusionReactor, shows normal JVM heap memory and CPU isn't maxed and has no active requests running; MySQL doesn't show a bunch of slow queries. The CF exception logs don't show anything amiss until a restart when I get a warning about a possible memory leak.
This has been very frustrating because it just stops working at random intervals.
Two months ago, I posted this with no replies:
Still having this problem too and it's driving me nuts. I don't know what changed, because CF10 was working fine for a while. Now Coldfusion stops responding one or more times a day with a number of threads in the wait chain. The only way to fix it is to restart the service. When I do, I get the same error messages as others in this thread in the Coldfusion-error.log on startup:
"SEVERE: The web application [/] created a ThreadLocal with key of type [coldfusion.util.DateUtils$1].....Threads are going to be renewed over time to try and avoid a probable memory leak."
Some of these are followed by this error message somehow related to Solr collections:
"SEVERE: The web application [/] created a ThreadLocal with key of type [org.apache.solr.common.util.DateUtil.ThreadLocalDateFormat] (value [org.apache.solr.common.util.DateUtil$ThreadLocalDateFormat@a95aa91]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@5af7aed5]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak."
May 01, 2014 9:11:28 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
It seems like the number of errors is about the same as the number of scheduled tasks. It doesn't look like any useful error, exception, or access messages get logged before Coldfusion stops responding.
My setup is a virtualized 2008 Win Server-64bit, Apache 2.2 (stock 32bit), CF10-64bit, update 13
I've tried:
- Various security improvements
- Searching for cfml errors or recursive code
- Adding RAM (8GB now)
- Pausing scheduled tasks
- Removing & reconnecting the server connector as Administrator as suggested
- Increasing the JVM heap size
- Using the latest 1.7.0_55 JRE externally
Next I guess I'll have to try reinstalling Coldfusion or rebuilding the server from scratch. I have to say that moving to Railo is looking more appealing than upgrading to CF11. This should just work without so much grief...