What do you mean an empty handler? Can you provide a sample please?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/tTjO8iv_m4UJ.
To post to this g
I use cron job to drive my backend. As soon as I put an empty handler
to /_ah/start, it started to work.
HIH,
Will
On Mon, Sep 26, 2011 at 8:14 AM, Jay Meydad wrote:
> Thanks for the suggestion. I fixed the yaml files however the tasks are
> still queued and not being processed.
> To clarify, t
Thanks for the suggestion. I fixed the yaml files however the tasks are
still queued and not being processed.
To clarify, the /_ah/start error occurs only if I force the task to run from
the Task Queues viewer.
--
You received this message because you are subscribed to the Google Groups
"Goo
Not sure if this helps, but yaml requires a space after the : in a mapping.
ie. use target: worker, not target:worker
Yes, Yaml can be picky. The parser used here may or may not be lenient, so
it's safer to be compliant.
--
You received this message because you are subscribed to the Google Gro
Rishi and all,
I followed what's in the thread but things are still not working for me.
Perhaps someone could assist / clarify exactly how things are defined on
your end.
In my app, all user-facing requests should be handled by the front-end code
& the backend, named 'worker', should handle a
Oh yeah, I guessed the *--backends* flag on *appcfg.py update *was
intended as a replacement for running a separate backends update each time.
Steve
On 11-09-09 06:22 PM, Rishi Arora wrote:
Found my problem. Looks like I must execute that appcfg.py update
backends command each time I make a c
Found my problem. Looks like I must execute that appcfg.py update backends
command each time I make a code change. It seems obvious now, but of
course, it never occurred to me! I'm all good now, even with countdown set
to 0, and tasqueue target set to either instance.backend_name or just
backend
I came across this (
http://code.google.com/appengine/docs/python/taskqueue/overview-push.html#Push_Queues_and_Backends).
Which suggests that I should be able to use a specific backend instance.
Not only was the backend started (really, enabled), but it was up and
running too, from serving up a r
I'm able to direct tasks to the backends using the *target* arg as in
your example. And the backend state is 'start' when you're trying this?
Are you directing toward a specific backend instance (/N.backend_name/)
or just to /backend_name/? I am doing the latter.
Steve
On 11-09-09 05:00 PM
Thanks. Yes that worked for me. It just seems that backend documentation
isn't very intuitive. I couldn't tell from any of the online docs that
simply adding a backend to backends.yaml won't configure a backend for you.
It won't show up in the backends section of the admin console until you
exe
Also, you can do...
*
*
*appcfg.py update **--backends your_app*
*
*
*
*
Steve
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/gvpp7TaOlykJ.
To pos
Also, you can do...
*
*
*appcfg.py update **--backends /your_app*
*
*
*
*
Steve
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/7tFwG2wYt_8J.
To po
Turns out, in order to create and configure a backend, its not sufficient to
just add it in the backends.yaml file and deploy the app. I had to run this
appcfg command to create the backend:
appcfg.py backends update
On Fri, Sep 9, 2011 at 2:20 PM, Rishi Arora wrote:
> 1. Configuration: When
13 matches
Mail list logo
