Re: [web2py] Re: server function not triggered in some cases

The issues solved with a great help of Niphlod. I answered my own question on stackoverflow. please correct if it is not correct http://stackoverflow.com/questions/34661782/web2py-function-not-triggered-on-user-request/34895532#34895532 Thank you On Monday, January 18, 2016 at 1:54:48 PM

Re: [web2py] Re: server function not triggered in some cases

perfect. Glad that everything is working fine. On Wednesday, January 20, 2016 at 10:02:04 AM UTC+1, Yebach wrote: > > The issues solved with a great help of Niphlod. I answered my own question > on stackoverflow. > > please correct if it is not correct > > >

Re: [web2py] Re: server function not triggered in some cases

"neverending" for this sake is "running for more than the usual timeout imposed by webservers" which is 60 seconds. a task can be queued and also stopped via the scheduler APIs (queue_task and stop_task) On Monday, January 18, 2016 at 12:43:36 PM UTC+1, Yebach wrote: > > I do not think you

Re: [web2py] Re: server function not triggered in some cases

I do not think you can treat it as a never ending process. There is a *.exe program that is started when user sends request, and also user stops it whenever he/she wants. I do not know how to treat this kind of process.I tried with scheduler but there was the same problem I really need some

Re: [web2py] Re: server function not triggered in some cases

I'm sorry but you need to rephrase your issue then. On Monday, January 11, 2016 at 12:46:05 PM UTC+1, Yebach wrote: > > External process never drops dead. The request comes to server but > sometimes, the function that reads the file, an external process created is > not started. There are no

Re: [web2py] Re: server function not triggered in some cases

External process never drops dead. The request comes to server but sometimes, the function that reads the file, an external process created is not started. There are no issues with external process. 2016-01-08 17:23 GMT+01:00 Niphlod : > so what's the issue with web2py if

Re: [web2py] Re: server function not triggered in some cases

I went trough my code again This is the way i start my eternal process try: count = 0 while ( count < 10 and ( os.path.isfile(outPath))): count += 1 os.remove(outPath) time.sleep(0.05) # Run woshi engine path_1 =

Re: [web2py] Re: server function not triggered in some cases

sooo. finally. The external process is started from within web2py. Which is handled by a webserver. Which ALWAYS imposes a timeout. You can't start a neverending process inside a web request. That's why long-running processes NEED to be managed OUTSIDE web2py (and why web2py provides

Re: [web2py] Re: server function not triggered in some cases

It is external process 2016-01-08 11:04 GMT+01:00 Niphlod : > you're missing the point. the "calculation" is running inside the web2py > environment or on an external process ? > > > On Thursday, January 7, 2016 at 8:58:04 PM UTC+1, Yebach wrote: >> >> The calculation runs on

[web2py] Re: server function not triggered in some cases

you're missing the point. the "calculation" is running inside the web2py environment or on an external process ? On Thursday, January 7, 2016 at 8:58:04 PM UTC+1, Yebach wrote: > > The calculation runs on the same server. When user starts a calculation a > function creates a txt file and puts

Re: [web2py] Re: server function not triggered in some cases

so what's the issue with web2py if your external process sometimes drops dead ? who starts the external process ? On Friday, January 8, 2016 at 12:32:20 PM UTC+1, Yebach wrote: > > It is external process > > 2016-01-08 11:04 GMT+01:00 Niphlod : > >> you're missing the point.

[web2py] Re: server function not triggered in some cases

The calculation runs on the same server. When user starts a calculation a function creates a txt file and puts it in a folder in my application. The engine checks if the file is there. if file exists it starts a calculation. The way user stops calculation another function actually deletes that