tomcat - 404 Handler Hanging on ColdFusion 10, works perfect on ColdFusion 8 -

i'm having odd intermittent issue 404 handler pages on our coldfusion 10 server. here's backstory:

1. we have been running 2 load-balanced coldfusion 8 servers ages without issue.

2. we have upgraded 1 of these 2 servers coldfusion 10 in order soft-launch our coldfusion 10 upgrade.

3. i've installed update 8 on cf10 server, , have removed , re-added connectors.

4. both servers running windows 2008 r2.

i've read several forum posts stating issues people getting connection reset issues 404 pages, i'm not seeing particular issue. seeing hung thread in fusionreactor 404.cfm file. here's example of stacktrace taken 1 of these hung threads:

thread stack trace trace time:   07:02:14.638 04-mar-2013 request id:   179934 script name:  http://example.com/404.cfm?404;http://example.com:80/somemissingfile started:      06:07:17.581 04-mar-2013 exec time:    3297057ms memory used:  (32%)1,669,600kb memory free:  3,539,295kb thread id:    0x53de (21470) thread name:  ajp-bio-8012-exec-86 priority:     5 hashcode:     1636847260 state:        runnable  "ajp-bio-8012-exec-86" daemon prio=5 runnable  java.net.socketinputstream.socketread0(socketinputstream.java:???)[native method] java.net.socketinputstream.read(socketinputstream.java:129) org.apache.coyote.ajp.ajpprocessor.read(ajpprocessor.java:319) org.apache.coyote.ajp.ajpprocessor.readmessage(ajpprocessor.java:445) org.apache.coyote.ajp.ajpprocessor.receive(ajpprocessor.java:341) org.apache.coyote.ajp.abstractajpprocessor.finish(abstractajpprocessor.java:1032) org.apache.coyote.ajp.abstractajpprocessor.action(abstractajpprocessor.java:386) org.apache.coyote.response.action(response.java:170) org.apache.coyote.response.finish(response.java:276) org.apache.catalina.connector.outputbuffer.close(outputbuffer.java:288) org.apache.catalina.connector.coyoteoutputstream.close(coyoteoutputstream.java:108) com.intergral.fusionreactor.plugin.amf.interposeroutputstream.close(interposeroutputstream.java:104) com.intergral.fusionreactor.trackedstream.trackedstream.close(trackedstream.java:113) com.intergral.fusionreactor.filter.softkill.softkillresponsestream.close(softkillresponsestream.java:146) com.intergral.fusionreactor.filter.fusionreactorresponsewrapper.finish(fusionreactorresponsewrapper.java:192) com.intergral.fusionreactor.core.fusionreactor.finish(fusionreactor.java:683) com.intergral.fusionreactor.filter.fusionreactorcorefilter.dohttpservletrequest(fusionreactorcorefilter.java:575) com.intergral.fusionreactor.filter.fusionreactorcorefilter.dofusionrequest(fusionreactorcorefilter.java:337) com.intergral.fusionreactor.filter.fusionreactorcorefilter.dofilter(fusionreactorcorefilter.java:246) com.intergral.fusionreactor.filter.fusionreactorfilter.dofilter(fusionreactorfilter.java:121) org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:243) org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:210) org.apache.catalina.core.standardwrappervalve.invoke(standardwrappervalve.java:224) org.apache.catalina.core.standardcontextvalve.invoke(standardcontextvalve.java:169) org.apache.catalina.authenticator.authenticatorbase.invoke(authenticatorbase.java:472) org.apache.catalina.core.standardhostvalve.invoke(standardhostvalve.java:168) org.apache.catalina.valves.errorreportvalve.invoke(errorreportvalve.java:98) org.apache.catalina.valves.accesslogvalve.invoke(accesslogvalve.java:928) org.apache.catalina.core.standardenginevalve.invoke(standardenginevalve.java:118) org.apache.catalina.connector.coyoteadapter.service(coyoteadapter.java:414) org.apache.coyote.ajp.ajpprocessor.process(ajpprocessor.java:204) org.apache.coyote.abstractprotocol$abstractconnectionhandler.process(abstractprotocol.java:539) org.apache.tomcat.util.net.jioendpoint$socketprocessor.run(jioendpoint.java:298) java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:895) java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:918) java.lang.thread.run(thread.java:662) 

i've tried manually killing these threads through fusionreactor, won't die. way clear hung threads restart coldfusion service (which i've had @ least once day since upgraded coldfusion 10.

the 404 doesn't special other run our standard layout custom tag , display page not found notification.

looking @ thread dump appears coldfusion has finished doing processing , completed filling buffer output, it's not finishing sending browser?

org.apache.coyote.ajp.abstractajpprocessor.finish(abstractajpprocessor.java:1032) org.apache.coyote.ajp.abstractajpprocessor.action(abstractajpprocessor.java:386) org.apache.coyote.response.action(response.java:170) org.apache.coyote.response.finish(response.java:276) org.apache.catalina.connector.outputbuffer.close(outputbuffer.java:288) org.apache.catalina.connector.coyoteoutputstream.close(coyoteoutputstream.java:108) 

there's lots of stuff there closing , finishing, steps following have more reads , responses. i'm not sure might happening here, it's stalling completion of our coldfusion 10 migration. need discover what's causing these hung threads.

what experiencing same bug encountered in january. i've logged bug in adobe's bugbase:

https://bugbase.adobe.com/index.cfm?event=bug&id=3494728

their engineering team has acknowledged issue, no eta on actual fix. adobe's connector iis in cf10 has been quite troublesome us. can set timeout kill these hanging threads listed in workaround, @ least keep having reboot server daily. luck!