[frs-25] Why doesn’t soft kill always work? (Understanding Soft Kill Limitations)

When you select a thread or request to be stopped using the red 'X' icon, FusionReactor first attempts to stop the request using 'Soft Kill'. This causes FusionReactor to attempt to kill the thread by stopping the request inside the J2EE engine.

FusionReactor attempts this first because it is a more stable method of stopping a request than using an outright thread kill.

Unfortunately, because of the way J2EE requests are handled, Soft Kill can only be used in two situations:

  • The request is currently outputting data to the page.
  • The request is currently transferring JDBC data from a result set.

The latter condition requires you to wrap your datasources using the ColdFusion MX JDBC Driver Wrapper.

If the request is not currently outputting data or transferring JDBC results, the soft kill will time out, and FusionReactor will attempt a thread kill.

Issue Details

Type: Technote
Issue Number: FRS-25
Components: Request Managment, Thread Management
Environment:
Resolution: Fixed
Last Updated: 18/Jan/08 8:21 PM
Affects Version: 2.0
Fixed Version: 2.0
Server:
Platform:
Related Issues:

FRS-26: I’m using the FusionReactor JDBC Driver Wrapper and I can see in FusionReactor’s JDBC view that the query is running, but Soft Kill still doesn’t work.

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.