Java 8 has reached end of support
and will be
deprecated
on January 31, 2026. After deprecation, you won't be able to deploy Java 8
applications, even if your organization previously used an organization policy to
re-enable deployments of legacy runtimes. Your existing Java
8 applications will continue to run and receive traffic after their
deprecation date. We recommend that
you
migrate to the latest supported version of Java.
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-08-25 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-08-25 UTC."],[[["\u003cp\u003eThis API is for first-generation runtimes, and users upgrading to second-generation runtimes should consult the migration guide for legacy bundled service migration options.\u003c/p\u003e\n"],["\u003cp\u003eThe local development server (\u003ccode\u003edev_appserver\u003c/code\u003e) for push queues has limitations, as it does not respect the \u003ccode\u003erate\u003c/code\u003e and \u003ccode\u003ebucket-size\u003c/code\u003e attributes.\u003c/p\u003e\n"],["\u003cp\u003eThe development server does not preserve queue state across restarts, leading to a loss of queue information.\u003c/p\u003e\n"],["\u003cp\u003eTasks on the development server are executed as close to their ETA as possible, regardless of the queue's specified rate, and a rate of \u003ccode\u003e0\u003c/code\u003e does not prevent execution.\u003c/p\u003e\n"],["\u003cp\u003eYou can prevent automatic push task execution in the development server by setting the JVM flag \u003ccode\u003e-Dtask_queue.disable_auto_task_execution=true\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Testing Push Queues in the Development Server\n\n| This API is supported for first-generation runtimes and can be used when [upgrading to corresponding second-generation runtimes](/appengine/docs/standard/\n| java-gen2\n|\n| /services/access). If you are updating to the App Engine Java 11/17 runtime, refer to the [migration guide](/appengine/migration-center/standard/migrate-to-second-gen/java-differences) to learn about your migration options for legacy bundled services.\n\nThis page describes some limitations with using the local development server\n(`dev_appserver`) to test push queues in your application. In most\nrespects, you set up your queues and tasks just as you would to run them in the\nApp Engine production environment, but there are some differences:\n\n- 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.\n- The development server doesn't preserve queue state across restarts.\n\nTo prevent push tasks from running in the development server at all, use the\nfollowing JVM flag when you start the server: \n\n dev_appserver.sh --jvm_flag=-Dtask_queue.disable_auto_task_execution=true"]]
