App Engine standard environment for Java 11, Java 17, and Java 21 release notes

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.

December 09, 2024

Custom organization policies for Serverless VPC Access connectors are now generally available, and can be applied to projects, folders, or organizations.

October 31, 2024

Java 11 has reached end of support. Your existing Java 11 applications using will continue to run and receive traffic. However, App Engine might block re-deployments of applications that use runtimes after their end of support date. We recommend that you upgrade to the latest supported version of Java.

July 30, 2024

In the App Engine page in the Google Cloud console, you can now filter your existing App Engine versions by runtime lifecycle stages. After you apply this filter, the console displays a warning icon for App Engine versions that are approaching end of support, have reached end of support, are deprecated, and are decomissioned.

July 16, 2024

You can now configure an HTTP connector to improve CPU and memory utilization for your App Engine apps. To configure an HTTP connector, include the appengine.use.httpconnector system property in your appengine-web.xml file. For more information, see Google App Engine Java new performant HTTP connector GitHub page.

July 12, 2024

Deployments for new projects might be impacted from the following changes to org policies:

  • Starting in May 2024, Google Cloud enforces secure-by-default organization policies for all organization resources. This policy prevents App Engine from granting the Editor role to the App Engine default services accounts by default.

  • Starting in June 2024, Cloud Build has changed the default behavior for how Cloud Build uses service accounts in new projects. This change is detailed in Cloud Build Service Account Change. As a result of this change, new projects deploying versions for the first time may be using the default App Engine service account with insufficient permissions for deploying versions.

If you are impacted by this change you can do one of the following:

  • Grant the Editor role to the App Engine default service account.

  • Review the Cloud Build guidance on changes to the default service account and opt out of these changes.

February 26, 2024

January 23, 2024

The option to update a Serverless VPC Access connector is now available at general availability (GA). This feature allows you to edit the machine (instance) type, as well as the minimum and maximum number of instances.

December 21, 2023

A warning message now appears before you publish a container image to a public repository.

December 06, 2023

Java 21 is now available in preview. Update your configuration files based on either of the following options, depending on what your app currently uses:

  • If you use legacy bundled services, you must upgrade your apps to run on either:

    • Java Enterprise Edition 10 (EE10 - default, recommended): Java EE10 does not support javax.servlet.* APIs and requires you to update your apps and third-party dependencies to use newer Java artifacts like the Jakarta namespace.
    • Java Enterprise Edition 8 (EE8): Java EE8 lets you use javax.servlet.* APIs, but you must make minor configuration changes to your appengine-web.xml file.

  • If you don't use legacy bundled services, update the version in your app.yaml file.

    See Upgrade an existing application for all options.

August 07, 2023

Accessing a service that's prohibited by the Internal or Internal and Cloud Load Balancing ingress setting now results in a 404 rather than 403 error code.

June 22, 2023

The Java runtime now supports using Maven wrappers for managing your project's dependency on Maven.

May 01, 2023

Memory limits for second-generation runtimes have been increased to better support the growing memory utilization of many newer runtimes.

April 27, 2023

The Search API is now available in the App Engine legacy bundled services for second-generation runtimes. Access this legacy bundled service through the App Engine API JAR.

April 18, 2023

  • Updated the Java SDK to version 2.0.13.
  • Upgraded Jetty web server to version 9.4.51.v20230217.

December 21, 2022

The option to update a Serverless VPC Access connector is now available in preview. This feature allows you to edit the machine (instance) type, as well as the minimum and maximum number of instances.

December 13, 2022

You can now use any configured service account in your Cloud project as the app-level default service account, while creating and updating your App Engine applications.

November 01, 2022

Build environment variables support is now generally available.

July 18, 2022

  • Updated the Java SDK to version 1.9.98.
  • Updated Jetty web server to version jetty-9.4.46.v20220331.

July 01, 2022

June 06, 2022

The Java 17 runtime (preview) now uses Ubuntu 22.

May 26, 2022

  • Updated the Java SDK to version 1.9.97.
  • Added missing classes in the appegine-jsr107cache.jar file.

May 18, 2022

Specifying a user-managed service account for each App Engine version during deployment is now generally available.

April 13, 2022

The App Engine legacy bundled services for Java 11/17 are now available at the General Availability release level. These APIs can be accessed through language-idiomatic libraries. Calls to these API are billed according to the standard rates.

April 08, 2022

  • Updated the Java SDK to version 1.9.96 to also support Java 17 (preview).
  • Updated Jetty web server to version 9.4.45.v20220203.

March 24, 2022

Support for Serverless VPC Access connectors in Shared VPC host projects is now at general availability (GA). Learn about the advantages of this method and how to configure connectors in host projects.

March 15, 2022

All released artifacts that start with version 2.x.x use the open source release mechanism. Released artifacts that start with version 1.9.9xx or earlier use the internal build system. See the appengine-java-standard repository for more details.

March 14, 2022

February 17, 2022

Updated the Java SDK to version 1.9.95.

January 28, 2022

Builds are now handled by regional Cloud Build pools within the selected App Engine region. To view build logs, go to Cloud Build in the Cloud Console, select the History page, and select the region you would like to filter by.

January 19, 2022

Updated Java SDK to version 1.9.94.

December 01, 2021

Updated Java SDK to version 1.9.93.

November 03, 2021

Egress settings for Serverless VPC Access are now generally available. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.

November 02, 2021

  • Upgrade to Jetty version 9.4.44.v20210927

September 27, 2021

Many legacy App Engine APIs are now available to select second-generation runtimes. These APIs are available for Java 11 in preview, through language-idiomatic libraries. Calls to these APIs are billed according to the standard rates.

July 21, 2021

Egress settings are now available for Serverless VPC Access. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.

July 16, 2021

  • Updated Java SDK to version 1.9.90.

June 30, 2021

Specifying a user-managed service account for each App Engine version during deployment is now available in preview. This feature lets you grant different privileges to each version, based on the specific tasks it performs, and avoid granting more privileges than necessary.

Requests from newly created or updated App Engine Cron jobs sent to the App Engine standard environment now come from 0.1.0.2. For Cron jobs created with older gcloud versions (earlier than 326.0.0), Cron requests will come from 0.1.0.1. Previously, these requests only came from 0.1.0.1. See Understanding the App Engine firewall for more information.

June 14, 2021

App Engine is now available in the us-west1 (Oregon), asia-southeast1 (Singapore), and asia-east1 (Taiwan) regions.

May 20, 2021

  • Updated Java SDK to version 1.9.89.
  • Upgraded to Jetty version 9.4.41.v20210516.
  • Stopped releasing Maven artifact appengine-api-labs-1.9.xx.jar. Last release is 1.9.88.

April 27, 2021

Automatic scaling elements min_instances and min_idle_instances will now only apply to versions of a service that have been configured to receive traffic. This change is to reduce unexpected billing due to instances running old versions that are not intended to receive traffic.

April 20, 2021

Build environment variables support is now available in preview.

April 14, 2021

Serverless VPC Access support for Shared VPC is now generally available.

April 13, 2021

App Engine is now available in the europe-central2 region (Warsaw).

April 01, 2021

  • Updated Java SDK to version 1.9.88.
  • Upgraded to Jetty 9.4.39 to fix CVE-2021-28163, CVE-2021-28164, CVE-2021-28165.

March 26, 2021

App Engine standard environment provides a new metric, CPU Utilization, which indicates the CPU utilization average over all active instances. For more information, see Google Cloud metrics.

November 12, 2020

You can use network ingress controls so your app only receives requests that are sent from your project's VPC or that are routed through the Cloud Load Balancing load balancer. This feature is now generally available.

September 25, 2020

If you use Cloud Load Balancing, you can use network ingress controls so your app only receives requests that are routed through the load balancer.

July 23, 2020

July 08, 2020

External HTTP(S) Load Balancing is now supported for App Engine via Serverless network endpoint groups. Notably, this feature allows you to use Cloud CDN with App Engine.
This feature is available in Beta.

June 08, 2020

App Engine is now available in the asia-southeast2 region (Jakarta).

May 14, 2020

To get a fine-grained view of billing data for each resource used by your App Engine services, you can apply labels to the services, export your billing data to BigQuery, and run queries. For more information, see Labeling App Engine resources.

April 20, 2020

App Engine is now available in the us-west4 region (Las Vegas, NV).

March 13, 2020

App Engine is now available in the asia-northeast3 region (Seoul).

March 06, 2020

App Engine is now available in the us-west3 region (Salt Lake City, Utah).

February 11, 2020

App Engine is changing the URLs that you use to send requests to your apps. URLs now include a region ID to help Google route your requests more efficiently and reliably. For example, an app can receive requests at https://<var>PROJECT_ID</var>.<var>REGION_ID</var>.r.appspot.com. This new URL is optional for existing apps and is provided for all new apps.

To ensure a smooth transition, we are slowly updating App Engine to use region IDs. If we haven't updated your Google Cloud project yet, you won't see a region ID for your app. Since the ID is optional for existing apps, you don't need to update URLs or make other changes once the region ID is available for your existing apps.

February 06, 2020

  • You can no longer apply new spending limits to projects. Existing spending limits will continue to work. For more information on how you can limit app costs, see Limiting Costs.

December 11, 2019

December 07, 2019

  • Updated Java SDK to version 1.9.77.
  • Upgrade Jarkata Jasper JSP compiler to version 9.0.24.

October 17, 2019

July 30, 2019

  • The AppCfg tooling and the legacy standalone App Engine SDK, delivered through the GoogleAppEngineLauncher.dmg, GoogleAppEngine.msi, and google_appengine.zip files, are now deprecated. Google will shut down and remove support on July 30, 2020.

June 24, 2019

  • Updated Java SDK to version 1.9.76.

June 05, 2019

June 03, 2019

  • Updated Java SDK to version 1.9.75.
  • The Google App Engine API jar is now compiled as a Java 8 target.
  • Fixed performance issue for large batch GETs from Memcache.

April 30, 2019

  • Updated Java SDK to version 1.9.74.

April 18, 2019

  • App Engine is now available in the asia-northeast2 region (Osaka, Japan).

April 15, 2019

  • App Engine is now available in the europe-west6 region (Zürich, Switzerland).

March 26, 2019

  • Updated Java SDK to version 1.9.73.

February 13, 2019

  • Updated Java SDK to version 1.9.72.
  • You can no longer build Java 7 apps. Java 7 app deployment was blocked on January 25.

January 25, 2019

  • App deployments on the Java 7 runtime are now blocked. If your app is currently using the Java 7 runtime, it will be automatically migrated to the Java 8 runtime.

January 21, 2019

  • Updated Java SDK to version 1.9.78.

December 28, 2018

  • Updated Java SDK to version 1.9.69.
  • Upgrade the ASM library to improve handling of Java 11 bytecode.
  • Stop bundling the ECJ (Eclipse compiler) in the JSP compilation classpath.

December 19, 2018

  • Updated Java SDK to version 1.9.71.
  • DeleteSchema method in com.google.appengine.api.search.Index is now supported. To completely delete an index, you need to delete the index's documents and schema.

December 06, 2018

  • Updated Java SDK to version 1.9.70.
  • Updated Jetty to version 9.4.14.v20181114.

October 25, 2018

  • Updated Java SDK to version 1.9.68.
  • Minor bug fixes.

October 22, 2018

  • App Engine is now available in the asia-east2 region (Hong Kong).

October 18, 2018

  • Updated Java SDK to version 1.9.67.
  • AppEngineSession.setAttribute supports null values, fixing a bug that would previously throw null pointer exceptions.

October 03, 2018

  • Updated Java SDK to version 1.9.66.
  • Updated Jetty to version 9.4.12.v20180830.

September 19, 2018

Java runtime notes

  • Updated Java SDK to version 1.9.65.
  • enhance_jdos will fail if it raises an exception.
  • DatastoreType always returns high replication.
  • Fixed grammar in staging option defaults help.
  • Fixed LocalMailService javadoc.
  • min-instances can be set to 0 in appengine-web.xml.
  • Improved support for using Java 11 to develop and deploy apps on the Java 8 runtime.

August 24, 2018

Shutdown of Cloud Endpoints Frameworks v1 is approaching

Cloud Endpoints Frameworks v1 for the App Engine standard environment was deprecated on August 2, 2017. The service is scheduled to be shutdown on September 3, 2018, and the documentation will be removed. To avoid an outage, you must migrate your v1 application. For information on migrating your application to Endpoints Frameworks v2, see the following:

July 10, 2018

  • App Engine is now available in the us-west2 region (Los Angeles).

July 02, 2018

Fixed a bug in auto scaling configuration where App Engine was aggressively shutting down instances when the max-instances setting was used.

May 31, 2018

Java runtime notes

  • Updated Java SDK to version 1.9.64.
  • Adds --application flag to dev_appserver.py.
  • Prevent deployment with filenames containing carriage returns.
  • Fixes a problem where environment variables set in the appengine-web.xml file were not passed through the staging process and available to the app.

May 15, 2018

  • Completed a gradual rollout of an upgrade to the automatic scaling system:
    • Improved efficiency resulting generally in lower instance cost (up to 6% reduction for many users) and up to 30% reduction for loading requests, which are the first request to a new instance.
    • New max instances setting allows you to cap the total number of instances to be scheduled.
    • New min instances setting allows you to specify a minimum number of instance to keep running for your app.
    • New target CPU utilization setting lets you optimize between latency and cost.
    • New target throughput utilization setting lets you optimize for the number of concurrent requests at which new instances are started.
    • No more resident instances in auto scaling. Previously, if you used the min_idle_instances setting, the minimum idle instances were labelled as Resident in the Cloud Console, with the remainder of the instances labelled as Dynamic. The new scheduler simply labels all instances as Dynamic with auto scaling. However, the underlying behavior remains similar to previous behavior. If you use min_idle_instances and enable warmup requests, you will see at least that many dynamic instances running even during periods with no traffic.
    • For more details, see the auto scaling documentation.

February 27, 2018

Java runtime notes

  • Updated Java SDK to version 1.9.63.

February 07, 2018

Java runtime notes

  • Updated Java SDK to version 1.9.62.
  • Fixed a Cloud SDK issue where the Java 8 Servlet 3.1 quickstart processing failed during deployment.

January 22, 2018

Java runtime notes

  • Java SDK version 1.9.61 was patched. If you have previously installed this version, download and reinstall the SDK.

January 18, 2018

Java runtime notes

  • Updated Java SDK to version 1.9.61.

December 20, 2017

Java runtime notes

  • Updated Java SDK to version 1.9.60.
  • Added a deprecation warning when deploying or locally running a Java 7 application.
  • Fixed a bug when using the appcfg flag 'use_google_application_default_credentials' did not work correctly on Google Compute Engine VMs.
  • Added a new flag to the appcfg command called enable_new_staging_defaults to prepare for future Cloud SDK integration to provide better default values for Java application deployment flags.
  • Changed the default character encoding to UTF-8 in the local development server when the runtime is Java 8. Also, allow the character encoding to be set explicitly using the appengine.file.encoding system property. These changes mimic what happens in production.

December 14, 2017

Java runtime notes

  • Updated Java SDK to version 1.9.59.
  • Updated the local development server to set the url-stream-handler configuration parameter to native by default. This change reflects the behavior of the Java 8 runtime in production. For more information on url-stream-handler, see the appengine-web.xml reference.
  • Fixed the NoClassDefFoundError error that occurs when using the local development server with the Java 8 runtime and Endpoints Framework Gradle Plugin.

October 31, 2017

  • App Engine is now available in the asia-south1 region (Mumbai, India).

October 11, 2017

Java runtime notes

  • Updated Java SDK to version 1.9.58
  • Use 1.8 target for the Jetty 9 JSP compiler when using JDK 9.

September 25, 2017

Java runtime notes

  • Updated Java SDK to version 1.9.57
  • The local development server no longer supports -Xbootclasspath/p and google_sql.jar in the path.
  • The Java 8 runtime no longer supports JDK9 JARs that contain module-info.class.
  • Cloud Endpoints v1 is no longer supported on the Java 8 runtime.
  • Fixed NoClassDefFoundError exception on the local development server when using Cloud Endpoints v2 on the Java 8 runtime.

September 18, 2017

Java runtime notes

  • Release 1.3.3 for com.google.cloud.tools:appengine-gradle-plugin
  • The local development server now logs output to dev_appserver.out. (#156)
  • datastore-indexes-auto.xml is no longer removed during non-clean rebuilds. (#165)
  • Switched to use sync instead of copy on the explodeWar task. (#162)

September 13, 2017

  • You can now use managed certificates to add SSL to your custom domain. Once you map your custom domain to your application, App Engine provisions an SSL certificate automatically and handles renewing the certificate before it expires and revoking it if you remove the custom domain. Managed certificates are in beta. For more information, see Securing Custom Domains with SSL.

September 11, 2017

Java runtime notes

  • Updated Java SDK to version 1.9.56
  • For flexible runtimes compatible with the App Engine standard environment APIs (compat runtimes), this SDK version includes updates to the appengine-web.xml file configuration to add support for subnetwork_name, session_affinity, and updated liveness and readiness health checks.
  • Added support for the environment variables GAE_RUNTIME (java 7 or java 8) and GAE_ENV (standard) in the Google App Engine SDK.

September 05, 2017

  • App Engine is now available in the southamerica-east1 region (São Paulo, Brazil).
  • Updated Java SDK to version 1.9.55
  • Fixed bug where security manager was being used for the SDK even when the app was using Java 8/Jetty 9.
  • Emit error message when using the appstats filter with Java8.

August 01, 2017

  • App Engine is now available in the europe-west3 region (Frankfurt, Germany).

July 18, 2017

  • App Engine is now available in the australia-southeast1 region (Sydney, Australia).

June 28, 2017

What's New

Known Java 8 Runtime Limitations

  • The /tmp directory is writable. Files in /tmp will consume memory allocated to your instance.
  • Async Servlet 3.1 is not supported.
  • WebSocket is not supported.
  • The Jetty 9 configuration cannot be modified.
  • App Engine APIs can only be called from the thread that handles a web request or from threads created using ThreadManager
  • WEB-INF/appengine-web.xml must be used for configuration, app.yaml is not currently supported.
  • Deployment must be done through the Maven, Gradle, or IDE plugins.
  • If you create a thread pool using for example ExecutorService pool = Executors.newCachedThreadPool(ThreadManager.currentRequestThreadFactory()) then it must be shutdown down explicitly using pool.shutdown() before the current request terminates.
  • Previously it was possible to reference vendored classes like com.google.appengine.repackaged.org.joda.Instant inadvertently when just org.joda.Instant was intended. The vendoring scheme has changed so code that did that no longer works.
  • Native network APIs (for example HttpURLConnection) are enabled for billed applications, but will return an exception (java.net.SocketTimeoutException or java.io.IOException) when used in free applications. Free applications can access *.googleapis.com and accounts.google.com, and they can also be configured to use the URLFetch service.
  • The google-cloud-java APIs need to be wrapped in an executor. See Pub/Sub Publisher hangs unless submitted through an executor.
  • Cloud Endpoints must be migrated from v1 to v2.
  • Channels and XMPP APIs are not supported.
  • appengine-labs-api.jar APIs are not supported resulting in Appstats for Java not being supported.
  • The Java 8 runtime default is to use the native Java HTTP(S) transport, not the URL Fetch transport, as is the case for Java 7 runtime. For more information, see url-stream-handler.

June 15, 2017

  • Updated Java SDK to version 1.9.54.

June 06, 2017

  • App Engine is now available in the europe-west2 region (London).

May 09, 2017

  • App Engine is now available in the us-east4 region (North Virginia).
  • Updated Java SDK to version 1.9.53.
  • Fixed a Java SDK issue where JSP tag library usage would not work with a Java 8 SpringBoot application.

May 08, 2017

  • Release 1.3.1 for com.google.cloud.tools:appengine-(gradle/maven)-plugin
  • Running locally on development server will read and include environment variables from the appengine-web.xml configuration file.
  • Expose environment parameter for including additional environment variables through the maven/gradle configuration.

May 02, 2017

  • Release 1.3.0 for com.google.cloud.tools.appengine-(gradle/maven)-plugin
  • Default development server is Dev App Server v1 (only java modules)
  • New gradle tasks for configuration deployment : appengineDeployCron, appengineDeployDispatch, appengineDeployDos, appengineDeployIndex, appengineDeployQueue
  • New maven goals for configuration deployment : appengine:deployCron, appengine:deployDispatch, appengine:deployDos, appengine:deployIndex, appengine:deployQueue
  • Staging flexible apps with maven/gradle only copies app.yaml into build/target directory. For deployment of configuration files, use src/main/appengine.
  • Gradle exploded app directory default changed from build/exploded-app to build/exploded-<module-name>

April 19, 2017

  • Updated Java SDK to version 1.9.52.
  • Better support for Java 8 standard environment alpha runtime.
  • Upgrade to Jetty 9.3.18 for the Java 8 alpha standard environment runtime.
  • Update the quickstart-web.xml processing to use the latest Jetty capabilities to better support Java 8 SpringBoot applications.
  • Fix local execution of multiple services located in directories ending with the same name.
  • Fix SDK error when booting a SpringBoot application.

March 29, 2017

  • Updated Java SDK to version 1.9.51.

March 21, 2017

  • Updated the com.google.cloud.tools:appengine-gradle-plugin to 1.1.1.
  • Fixed issue 108 with flexible environment deployments in multi-module Gradle projects failing.

March 06, 2017

  • Updated the com.google.cloud.tools:appengine-maven-plugin to 1.2.1.
  • Fixed issue 144 with custom deployable parameters incorrectly adding in extra directory.

March 01, 2017

  • Updated Java SDK to version 1.9.50.
  • Added support for testing multiple services with the local development server.
  • Stop generating a web.xml file for apps that use the Java 7 runtime and include a web.xml that specifies the servlet 3.1 schema.
  • Package Java class files in the .zip files even if the application does not have JSPs.

February 17, 2017

Updated the com.google.cloud.tools maven (1.2.0) and gradle (1.1.0) plugins for App Engine:

  • Added clearDatastore flag for clearing the local datastore upon startup.
  • Added source-context tasks/goals.

January 30, 2017

  • Updated Java SDK to version 1.9.49.

December 01, 2016

  • Updated Java SDK to version 1.9.48.

November 03, 2016

  • Version 1.9.45 was skipped.
  • Updated Java Runtime and SDK to version 1.9.46.

October 27, 2016

  • The Channel and XMPP services are now deprecated. These services will be turned down on October 31, 2017.

October 17, 2016

  • Updated Java Runtime and SDK to version 1.9.44.
  • Add new BlobInfo property, which is set when a Blobstore blob is stored in a Cloud Storage bucket.

August 01, 2016

Admin API notes

  • Version 1 of the Admin API is now generally available.

Version 1.9.42

  • Version 1.9.41 was skipped.
  • Version 1.9.42 includes general bug fixes and improvements.

July 21, 2016

Java 11 runtime notes

  • Fixes potentially incorrect reported memory usage in the App Engine dashboard (the values under Instance "Average Memory" and the "Memory Usage" graph). This issue does not affect billing.

July 18, 2016

Version 1.9.40

  • Version 1.9.39 was skipped.
  • LeaseTasksByTag requests will be limited to 25 requests per second.
  • Server Errors and Client Errors now more accurately reflect per-URL status errors in the App Engine dashboard.
  • New App Engine guided walkthrough in the Cloud Console. Pick your preferred language and launch an interactive tutorial directly in the console.
  • Increases the maximum cron tasks limit to 250.

Java runtime notes

  • All Java applications will be automatically upgraded to use the 64-bit version of the Java runtime. This rolling upgrade will start on July 20, 2016.

July 01, 2016

Cloud Datastore

May 25, 2016

Version 1.9.38

  • The error returned by URL Fetch for a request to a port outside of the permitted ranges (80-90, 440-450, 1024-65535) will now always return INVALID_URL as documented.

Cloud Datastore

  • When committing a cross-group transaction, version numbers returned for new or updated entities are all the same. With the previous behavior, entities within the same group committed as part of a cross-group transaction, had the same version number, but entities in different groups might have had different version numbers. This change ensures all new and updated entities have an identical version number, regardless of their entity group, when committed as part of a cross-group transaction. As before, entities that are not updated will not have a new version number.

May 04, 2016

Version 1.9.37

Includes general bug fixes and improvements.

May 02, 2016

App Engine flexible environment

  • The Ruby runtime is now available for the App Engine flexible environment.

April 18, 2016

Version 1.9.36

In response to your requests, the App Engine Users API joins the rest of App Engine in supporting IAM roles and group expansion. This means that any user who is a project Owner, Editor or Viewer or an App Engine Admin is considered an "admin" by the Users API, regardless of whether the user was granted the role directly or by membership in a group. * This release populates error details, when available, in error messages associated with the "OverQuota" exception type.

Java runtime notes

  • Google no longer accepts quota increase requests for the mail service. Customers should use Sendgrid instead.

March 24, 2016

Version 1.9.35

  • Fixes trace timestamps to match log timestamps.

Java runtime notes

  • This release does not include a new Java SDK. Java users should continue to use the 1.9.34 SDK.

March 16, 2016

Java runtime notes

  • Version 1.9.34 of the Java SDK is available.

March 04, 2016

Version 1.9.34

  • Increases default quota for URL fetch for billed apps. Refer to the Quotas page for details.

Java runtime notes

  • This release does not include a new Java SDK. Java users should continue to use the 1.9.32 SDK.

February 17, 2016

Version 1.9.33

  • The URL path "/form" is now allowed and will be forwarded to applications. Previously, this path was blocked.

Java runtime notes

  • This release does not include a new Java SDK. Java users should continue to use the 1.9.32 SDK.

February 03, 2016

Version 1.9.32

  • Container construction choices for Managed VMs

    The gcloud preview app deploy (and mvn gcloud:deploy) commands upload your artifacts to our servers and build a container to deploy your app to the Managed VM environment.

    There are two mechanisms for building the container image remotely. The default behavior is to build the container on a transient Compute Engine Virtual Machine which has Docker installed. Alternatively, you can use the Cloud Build service. To use the Cloud Build service, follow these steps:

    1. Activate the Cloud Build API for your project.
    2. Use the command gcloud config set app/use_cloud_build True. This will cause all invocations of gcloud preview app deploy to use the service. (To return to the default behavior, use the command gcloud config set app/use_cloud_build False.

Java runtime notes

  • Improved exception handling for the low-level API for Datastore, Transaction.rollback(). Instead of an exception, it generates an INFO log message when an operation associated with the transaction has failed.

January 14, 2016

Version 1.9.31

App Engine now supports Google Groups: Adding a Google Group as a member of a project grants the members of the group access to App Engine. For example, if a Google Group is an Editor on a project, all members of the group now have Editor access to the App Engine application.

December 30, 2015

Version 1.9.30

Headers for push queue requests made for Task Queue tasks with no payload will now contain a Content-Length entry set to '0'. Previously headers for such requests contained no Content-Length entry.

Version 1.9.29

  • Stop calculating and storing queue depth for non-existent queues, queues marked for deletion, and in the case of queue table outages.
  • For developers using the endpoints API, added a discoverable boolean parameter to the @Api annotation to allow users to disable API discovery. Using this feature will prevent some client libraries (e.g. JavaScript) and the API Explorer from working, as they depend on discovery.

October 29, 2015

Version 1.9.28

The Prospective Search API, which was deprecated on July 14, 2015, is now restricted to existing users. It will fully shutdown on December 1, 2015.

Improved accuracy of Geo filtering in Search queries.

Java runtime notes

  • Disabled Files API in the Java DevAppServer.

September 25, 2015

Version 1.9.27

Applications that are newly enabled for billing now default to an unlimited daily budget, and no longer default to a maximum daily budget of $0. This prevents unwanted outages due to running out of budget. To set a ceiling on your application's daily cost, after you enable billing, set a budget in the app engine settings. For more information, see Setting a daily budget.

Datastore

  • Bugfix: Repeated numeric facets are now allowed.
  • Faceted Search is now GA.

August 27, 2015

Version 1.9.26

  • oauth2client library upgraded to version 1.4.2
  • Adds "show in context" menu for MVM application logs that have thread_id or request_id as a field in their log entry. This allows sorting app logs based on either field.
  • Capability to provision applications for current load and configure elastic provisioning based on both VM and application level metrics.
  • Remote API can now be accessed using OAuth2 credentials using https://developers.google.com/identity/protocols/application-default-credentials
  • Use RequestPayloadTooLargeException for URLFetch requests with payloads that are too large.

Java runtime notes

  • Java's URLFetch API gains a property to specify default fetch deadline. appengine.api.urlfetch.defaultDeadline is a floating point number in seconds that can be used to specify a default URLFetch timeout for Java in appengine-web.xml.

August 14, 2015

Version 1.9.25

  • Added PyAMF version 0.7.2 (Beta).
  • Admin Console menus start redirecting to Cloud Console. Select services such as the Admin Logs will continue to be available in the Admin Console.
  • Datastore now allows properties to represent the empty list.
  • Failed tasks in queues configured with a retry_limit of zero will no longer be retried.