I can understand something like a timeout occurs with the connection,
but I don't understand why apache starts it over in another process.
From what you say I can only gather that the new computation is started
from the beginning and the state of the former lost. What do you read
from the logs? If it's just a problem of connection timeout I think you
can keep it alive just sending to the client some character from time to
time during the computation flushing the channel after calling puts...
apt-cache-ng is repository cache for Debian/Ubuntu and has a web
interface for the database diagnostics and maintenance. Some of the
maintenance tasks take several minutes and the process never stops, but
it sends some feedback to the client
let me know
-- Massimo
On 11/22/2014 12:26 PM, Georgios Petasis wrote:
Hi all,
I have a quite lengthy computation exposed as a service through rivet.
What I have observed, is that apache after some time,
thinks that the process running my computation has stuck, and starts the
same computation in a second process.
Is there a way to avoid this?
Regards,
George
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
