ColdFusion MX: ''Connection reset'' errorsProducts affected
Connection reset errors in the default-event.log file are common and can usually be ignored. They are typically caused by a client browser canceling the request or another benign issue.
The error typically appears as follows:
03/15 12:28:33 error Connection reset java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at jrun.servlet.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:530) at jrun.servlet.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:522) at jrun.servlet.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:540) at jrun.servlet.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:229) at jrun.servlet.jrpp.JRunProxyService.swapRunnable(JRunProxyService.java:144) at jrunx.scheduler.ThreadPool$DownstreamMetrics.swapRunnable(ThreadPool.java:320) at jrunx.scheduler.ThreadPool$ThreadThrottle.swapRunnable(ThreadPool.java:433) at jrunx.scheduler.ThreadPool$UpstreamMetrics.swapRunnable(ThreadPool.java:280) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:76)
When this error occurs, it indicates that the ColdFusion/JRun process has lost its connection to the web server process. The following are two reasons why this may occur:
- The web server was stopped.
- A client, such as a web browser, was disconnected because the user clicked another link, closed the browser window, or hit stop or cancel. This can happen while the client is receiving a long response and neither ColdFusion nor the web server reserved enough buffer space for the unsent portion of the response.
When the second situation happens, a new connection will immediately be established between ColdFusion and the web server. Since the browser has already disconnected, no error message is seen by the end user.
If this error is displayed excessively in the logs, it may be an indication of slow site performance resulting in users becoming impatient and clicking another link before the page has completed downloading.
Additional Information
Doc ID
(tn_19331)
Last updated
2005-05-11
Products affected
