CODEWITHSUNDEEP
pythongoogle-app-engine
DurhamG
DurhamG

Reputation: 222

Can AppEngine python threads last longer than the original request?

We're trying to use the new python 2.7 threading ability in Google App Engine and it seems like the created thread is getting killed before it finishes running. Our scenario:

My assumption was that the thread would continue to run after the request had returned, as long as it did not exceed the total request time limit. What we're seeing though is that the thread is randomly killed partway through it's execution. No exceptions, no errors, nothing. It just stops running.

Are threads allowed to exist after the response has been returned? This does not repro on the dev server, only on live servers.

We could of course use a task queue instead, but that's a real pain since we'd have to set up a url for the action and serialize/deserialize the data.

Upvotes: 2

Views: 213

Answers (2)

Daniel Roseman
Daniel Roseman

Reputation: 600059

Deferred tasks are the way to do this. You don't need a URL or serialization to use them:

from google.appengine.ext import deferred
deferred.defer(myfunction, arg1, arg2)

Upvotes: 3

Amy U.
Amy U.

Reputation: 2237

The 'Sandboxing' section of this page: http://code.google.com/appengine/docs/python/python27/using27.html#Sandboxing indicates that threads cannot run past the end of the request.

Upvotes: 5

Related Questions