Blocking long response in 5.2.4
Blocking long response in 5.2.4
- Subject: Blocking long response in 5.2.4
- From: Thomas <email@hidden>
- Date: Thu, 12 May 2005 16:32:22 +1000
For many years I have had a number of computationally-intensive
calculations performed in a separate thread using a modified version
of WOLongResponsePage. The pages reloaded every 10 seconds, sometimes
for hours, and happily served up the final result.
Now in WO 5.2.4, the responses stop after a small but apparently
random number of reloads. The calculation thread keeps running, but
the application no longer responds to HTTP requests, even after the
calculation is finished and the thread deleted.
I thought it might be an editing context lock issue, but I've tried
using a new EC for the thread, with no change.
One clue is that it would never even serve the first long response
status page, until I added a one-second sleep near the start of the
calculation thread, which gave the application time to serve the
first page. After that it sometimes serves a few refreshes then gets
stuck.
Of course Apple's Long Response example works fine, even when I move
the code into my application, but it does nothing with EO objects.
I had an idea it might be the communication between the thread and
the page (updating the status), but even with that disabled, the same
thing occurs.
Any ideas would be greatly appreciated.
Thomas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden