在Google App Engine上从Java 7迁移到Java 8时出现Memory Error/500 Error [英] Memory Error/500 Error when migrating from Java 7 to Java 8 on Google App Engine

问题描述

从Java 7迁移到8之后，您的项目可能会出现500错误率的增加，并且您可能会看到此错误:

After Java 7 to 8 migration, your project may exhibit an increased 500 error rate and you may see this error:

Uncaught exception from servlet java.lang.OutOfMemoryError: Java heap space

推荐答案

在Google App Engine的标准环境中运行的每个应用程序都有一个实例类，该实例类确定其计算资源.

Each application running in the standard environment on Google App Engine has an instance class, which determines its compute resources.

B2实例类(或以下)可能不再足够大，我们建议升级到B4实例.

A B2 instance class (or below) may no longer big enough and we recommend upgrading to a B4 instance.

有关实例类的更多信息，请参见 https://cloud.google. com/appengine/docs/standard/#instance_classes

For more information on instance classes, see https://cloud.google.com/appengine/docs/standard/#instance_classes

有关实例类实现的详细信息，请参见 https://cloud.google.com/appengine/docs/standard/java/config/appref/#instance_class

For instance class implementation details, see https://cloud.google.com/appengine/docs/standard/java/config/appref/#instance_class

有关并发性和延迟的更多信息，请参见 https://cloud.google.com/appengine/docs/standard/java/runtime/#concurrency_and_latency

For more information on concurrency and latency, see https://cloud.google.com/appengine/docs/standard/java/runtime/#concurrency_and_latency

有关在Google App Engine上迁移到Java 8的更多提示，请参阅 https://cloud.google.com/appengine/docs/standard/java/migrating-to-java8

For more tips on migrating to Java 8 on Google App Engine, see https://cloud.google.com/appengine/docs/standard/java/migrating-to-java8

这篇关于在Google App Engine上从Java 7迁移到Java 8时出现Memory Error/500 Error的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！