Client request times out 2006-12-10 - By sb4
Back
We have a similar application, a Records Management System. We have not been
able to control the browser timeout either. We have some very long processes
(reports, textsearch index updates, etc.) that exceed the timeout.
Our workaround was to create a "job control" mechanism that received the
request and starts the report in it's own thread. (The job threads are held in
a global singleton hashmap.) The job control jsp then forwards to another jsp
that is a "job monitor" that displays the status of all running job threads.
Basically the "job monitor" jsp creates an HTML page with a javascript timer
that repeatedly posts back to the "job monitor" jsp to display the status of
all the jobs in the global hashmap every 5 seconds. When a job has
a "finished" status, the user can checkmark the job for display, and the next
time the page submits, the job monitor jsp forwards to a display jsp that is
associated with the checkmarked job (by design) and passes the hashmap key to
the display jsp. The display jsp uses the hashmap key to retrieve its "job"
object which is designed to retain any data for display. The display jsp then
formats the data into the HTML page for display. A separate menu item on our
User Interface lets the "job monitor" be displayed at any time.
Its a hefty system to get around the timeout problem, but the only solution we
have at the current time. It does have other benefits also in providing a way
to monitor various processing jobs that are running.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
