[frs-102] Sometimes Crash Protection does not kill long running requests.

The problem that you are seeing is most likely that the requests don't complete because they are waiting to send data to the browser. This is done via a "socket" which is a piece of native code that JRun uses to return the CF page contents. It can happen however that the browser that this receiving the content keeps the connection open but doesn't consume any of the content sent by JRun. This causes the situation that you see. FusionReactor unfortunately cannot kill these requests because of a limitation in Java itself that native code cannot be stopped. This is a known limitation of Java and there is no way around this in any of the current versions of Java.

It is known that Internet Explorer can create this problem due to a bug that it has of keeping the connection open when the window has been closed. Another common reason for this issue is Search Engine Spiders indexing and often following dead links or send invalid requests to servers resulting in many redirections. Finally you may be being attacked by software trying to do denial of service.

Issue Details

Type: Technote
Issue Number: FRS-102
Components: Crash Protection
Environment:
Resolution: Fixed
Last Updated: 09/Jul/07 4:08 PM
Affects Version:
Fixed Version:
Server:
Platform:
Related Issues:

FRS-114: When I kill a process, it times out and remains in the list as “Killing”. Shouldn’t this kill it immediately?

Comments are closed.