Open Microscopy Environment

Hi all,

From OMERO.web, I ran feature calculation on images under a dataset, which might take over serveral minutes. In this case, I know the feature calculation itself was done correctly, but after that, it does not refresh (or display) the template html file for the results.
I know it refreshes properly If the feature calculation process is done quickly (when there is no need to do the feature calculation).

Is there any regulation about the processing time (or time out) for a function in views.py?
if so, how can i extend it?

bk

bhcho wrote:Hi all,

From OMERO.web, I ran feature calculation on images under a dataset, which might take over serveral minutes. In this case, I know the feature calculation itself was done correctly, but after that, it does not refresh (or display) the template html file for the results.
I know it refreshes properly If the feature calculation process is done quickly (when there is no need to do the feature calculation).

Is there any regulation about the processing time (or time out) for a function in views.py?
if so, how can i extend it?

bk

Off hand there are two timeouts that you could potentially be hitting:

• The Nginx or Apache gateway timeout (you'd likely get an error if this timeout was reached)
• The browser's request timeout (you'd likely also get a "this server is not responding" or similar error if this timeout was reached)

The OMERO.web infrastructure itself should not terminate workers if they are running for a long time but the web browser timeouts are almost impossible to avoid. These timeouts are usually between 60-120 seconds and have to be changed in the browser.

If you have long running tasks you want to perform I'd advise you not to rely on just increasing these timeouts. You should perform the task in a way that does not require the browser, an OMERO.web worker or your web server (Apache or Nginx) to be blocked waiting on task for many minutes.