Why does the system sometimes lock up, or behave nondeterministically after killing a thread?
Description
When killing a request or thread, FusionReactor first tries to "soft-kill" it (which gives it the opportunity to end safely) but sometimes requests will not respond and we have to forcibly kill it using the most effective, non-blocking method available to us within the framework of the Java Virtual Machine. However, this method can theoretically leave the system in an inconsistent state. The chances of this happening are very low, but the system can be recovered by restarting ColdFusion MX. In practice we have never seen this case arise during development and testing.
Issue Details
| Type: | Technote |
|---|---|
| Issue Number: | FRS-20 |
| Components: | Request Managment |
| Environment: | |
| Resolution: | Fixed |
| Added: | 18/05/2007 12:02:04 |
| Affects Version: | |
| Fixed Version: | |
| Server: | |
| Platform: | |
| Related Issues: | None |
Issue Feedback
Did you find this issue helpful?
0 out of 0 people found this article helpful

