Why do I sometimes receive a JRun "application not ready" error after killing a JRun request?
Description
After stopping a thread or a request, JRun can take a short time to remove the stopped thread from the thread pool. During this time, the stopped thread may be selected for new requests from the pool by JRun. Unfortunately this isn't something that can be controlled from FusionReactor, but JRun will usually resolve this situation naturally. The worse case scenario is that you see one or two of these errors before JRun catches up.
Issue Details
| Type: | Technote |
|---|---|
| Issue Number: | FRS-19 |
| Components: | Request Managment |
| Environment: | |
| Resolution: | Fixed |
| Added: | 18/05/2007 12:00:56 |
| 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
