Re: ferret keeps running in case of LAS errors

[Jonathan Callahan <Jonathan.S.Callahan@xxxxxxxx>]

Martin,

Version 6.5 of LAS (which you've been having trouble installing) tries 
to address these issues.

In previous releases the LAS product server connected to Ferret and sent 
commands, waiting for Ferret to finish its work or send back an error 
message.  If you requested the identical product a second time, before 
the first request had finished, the LAS product server started up 
another process.

In version 6.5 the LAS product server will always return something after 
<ui_timeout> seconds (see the release notes).  If the product is 
finished it will return the requested product, otherwise the LAS product 
server will return a 'batch mode' page that allows the user to 1) 
monitor the progress of the result; 2) request email notification when 
it is finished; or 3) cancel the request.  Multiple requests for the 
same product will no longer result in multiple processes recreating the 
identical product.  Instead, additional requests will get the same 
'batch mode' response that the first request got.

These modifications are designed to solve exactly the problems you are 
mentioning.


-- Jon


Martin Schmidt wrote:

> Hi,
> I am confronted that ferret keeps running in the case of errors in 
> ferret scripts. Moreover, also
> if the access to LAS over the browser is finished it stays alive. 
> Accessing LAS again and
> encoutering another error a second instance of ferret keeps running. 
> After some time these
> processes occupy all memory and all processor power of the machine, 
> driving it into pageing.
>
> Finally all other processes freeze.
>
> Does anyone know a solution?
>
> Kind regards,
> Martin Schmidt