404处理程序挂在ColdFusion

404处理程序挂在ColdFusion

关注
发信
关注(28)粉丝(399)

404处理程序挂在ColdFusion 10上，在ColdFusion 8上工作完美

本文介绍了404处理程序挂在ColdFusion 10上，在ColdFusion 8上工作完美的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我在ColdFusion 10服务器上的404处理程序页面有一个奇怪的间歇性问题。这是后台：


  1. 我们一直在运行2个负载均衡的ColdFusion 8服务器， / li>

  2. 我们已将这两台服务器中的一台升级到ColdFusion 10，以便软启动ColdFusion 10升级。


  3. 我已在CF10服务器上安装了Update 8，并已删除并重新添加连接器。


  4. 两台服务器都运行Windows 2008 R2。


我已阅读过几篇论坛帖子，说明用户在404页面上遇到连接重置问题的问题，没有看到这个特定的问题。我看到的是一个挂钩线程在FusionReactor的404.cfm文件。下面是一个从这些挂起线程中取出的stacktrace的例子：

 线程栈跟踪
跟踪时间：07： 02：14.638 04-Mar-2013 
请求ID：179934 
脚本名称：http://example.com/404.cfm?404;http://example.com:80/somemissingfile 
开始于：06：07：17.581 2013年03月04日
执行时间：3297057ms 
内存使用：（32％）1,669,600KB 
内存空闲：3,539,295KB 
线程ID ：0x53de（21470）
线程名称：ajp-bio-8012-exec-86 
优先级：5 
 Hashcode：1636847260 
状态：RUNNABLE 
 
 ajp-bio-8012-exec-86daemon prio = 5 runnable 
 
 java.net.SocketInputStream.socketRead0（SocketInputStream.java：???）[Native方法] 
 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）



我试过通过FusionReactor手动杀死这些线程，但他们不会死。清除挂起线程的唯一方法是重新启动ColdFusion服务（自从我升级到ColdFusion 10以来，我每天至少要做一次）。



404不会运行我们的标准布局自定义标记，并显示一个没有找到页面的通知。



看看线程转储看来ColdFusion已经完成了

  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）

有很多东西有关关闭和整理，但它后面的步骤有更多的读取和响应。所以我不知道这里可能发生什么，但它肯定拖延了ColdFusion 10迁移的完成。

解决方案

你遇到的是我在1月遇到的同样的错误。我已经记录了Adobe的bug库中的错误：





他们的工程团队已经确认了这个问题，但没有实际修复的ETA。 Adobe的连接器在CF10的IIS一直是相当麻烦的我们。您可以设置超时，以杀死这些挂起的线程，如我的解决方法中所列，这将至少避免不必每天重新启动服务器。祝你好运！


I'm having an odd intermittent issue with the 404 handler pages on our ColdFusion 10 server. Here's the backstory:

  1. We have been running 2 load-balanced ColdFusion 8 servers for ages without issue.

  2. We have upgraded one of these two servers to ColdFusion 10 in order to soft-launch our ColdFusion 10 upgrade.

  3. I've installed Update 8 on the CF10 server, and have removed and re-added the connectors.

  4. Both servers are running Windows 2008 R2.

I've read several forum posts stating issues with people getting connection reset issues with their 404 pages, but I'm not seeing that particular issue. What I am seeing is a hung thread in FusionReactor for the 404.cfm file. Here's an example of the stacktrace taken from one 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, but they won't die. The only way to clear the hung threads is to restart the ColdFusion service (which I've had to do at least once a day since I upgraded to ColdFusion 10.

The 404 doesn't do anything special other than run our standard layout custom tag and display a page not found notification.

Looking at the thread dump it appears that ColdFusion has finished doing the processing and completed filling the buffer with output, but it's not finishing sending to the 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 about closing and finishing, but the steps following it have more reads and responses. So I'm not sure what might be happening here, but it's definitely stalling the completion of our ColdFusion 10 migration. I need to discover exactly what's causing these hung threads.

解决方案

What you are experiencing is the same bug I encountered in January. I've logged the bug in Adobe's bugbase:

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

Their engineering team has acknowledged the issue, but no ETA on an actual fix. Adobe's connector for IIS in CF10 has been quite troublesome for us. You can set a timeout to kill these hanging threads as listed in my workaround, which will at least keep you from having to reboot the server daily. Good luck!

这篇关于404处理程序挂在ColdFusion 10上，在ColdFusion 8上工作完美的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！

08-24 14:31
Powered by LMLPHP ©2024 404处理程序挂在ColdFusion 0.037508