views:

223

answers:

2

I have been testing the taskqueue with mixed success. Currently I am using the default queue, in default settings ect ect....

I have a test url setup which inserts about 8 tasks into the queue. With short order, all 8 are completed properly. So far so good.

The problem comes up when I re-load that url twice under say a minute. Now watching the task queue, all the tasks are added properly, but only the first batch execute it seems. But the "Run in Last Minute" # shows the right number of tasks being run....

The request logs tell a different story. They show only the first set of 8 running, but all task creation urls working successfully.

The oddness of this is that if I wait say a minute between the task creation url requests, it will work fine.

Oddly enough changing the bucket_size or execution speed does not seem to help. Only the first batch are executed. I have also reduced the number of requests all the way down to 2, and still found only the first 2 execute. Any others added display the same issues as above.

Any suggestions?

Thanks

A: 

When a task-queue ends in error : I believe it stays in your queue .. Check that

manatlan
The task queue does clear, which would make you assume it is executing. But there is nothing in the request logs. Its as it is not actually firing the task. Just removing it? Is that possible?
b3nw
Sorry for the late ...From my experience, when you do taskqueue : use log ! To see what's happening ... it's the only way to test that.The only thing I can tell, is that it seems that your taskqueues don't throw exception (so they are removed after the job)
manatlan
A: 

it seems I got the same problem. is there a solution now?

leon
forgive me. The default task request type is POST, but I only implement the get handle.
leon