Testing Push Queues in the Development Server
Stay organized with collections
Save and categorize content based on your preferences.
This page describes some limitations with using the local development server
(dev_appserver) to test push queues in your application. In most
respects, you set up your queues and tasks just as you would to run them in the
App Engine production environment, but there are some differences:
- The development server doesn't respect the
rate and bucket-size attributes
of your queues. As a result, tasks are executed as close to their ETA as
possible. Setting a rate of 0 doesn't prevent tasks from being executed
automatically.
- The development server doesn't preserve queue state across restarts.
To prevent push tasks from running in the development server at all, use the
following JVM flag when you start the server:
dev_appserver.sh --jvm_flag=-Dtask_queue.disable_auto_task_execution=true
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-01-28 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]
