Spring Boot Jetty无法在AppEngine Flexible中启动Sping Boot 应用程序

vof42yt1  于 2023-11-17  发布在  Spring
关注(0)|答案(1)|浏览(150)

注意：这是一个交叉帖子，因为我不确定这是一个技术问题还是一个bug，所以可以在here中找到这个bug。
几周前，我写了一个原型，用于向我们的appengine项目添加一个灵活的环境服务，该项目主要是标准环境服务。该原型基于java快速入门示例“HelloworldSpringBoot”，并进行了一些微小的修改。
在我成功地使用原型之后，我为这项服务转移到了一组更生产的代码，开发了几个星期，并试图在1月12日部署，4天前。该应用程序拒绝启动，经过几次尝试将应用程序简化为一个单一的路由，我无法让应用程序启动。
我切换回原型代码，部署到代码工作的原始项目，并看到应用程序未启动的相同行为。
没有一个错误消息指向，所以我有一对夫妇，我会在这里列出，可能是罪魁祸首。
第一个是最明显的，但可能是一个通用的包罗万象：

  1. Exception in thread "main" java.lang.IllegalStateException: No Available Context
  2.         at com.google.cloud.runtimes.jetty9.DeploymentCheck.lifeCycleStarted(DeploymentCheck.java:46)
  3.         at org.eclipse.jetty.util.component.AbstractLifeCycle.setStarted(AbstractLifeCycle.java:179)
  4.         at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
  5.         at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1511)
  6.         at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1438)
  7.         at java.security.AccessController.doPrivileged(Native Method)
  8.         at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1437)

字符串
接下来的事情发生在创业早期，但似乎是良性的：

  1. javax.servlet.ServletException: Not running on Jetty, JSR-356 support unavailable at org.eclipse.jetty.websocket.jsr356.server.deploy.WebSocketServerContainerInitializer.onStartup(WebSocketServerContainerInitializer.java:193) at org.eclipse.jetty.plus.annotation.ContainerInitializer.callStartup(ContainerInitializer.java:140) at org.eclipse.jetty.annotations.ServletContainerInitializersStarter.doStart(ServletContainerInitializersStarter.java:63) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:329) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1501) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1463) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:785) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41) at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:188) at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:502) at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:150) at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180) at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:447) at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64) at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610) at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529) at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392) at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:564) at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:239) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131) at org.eclipse.jetty.server.Server.start(Server.java:452) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.Server.doStart(Server.java:419) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1511) at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1438) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1437)

型
然后有这个家伙，发生在前一个：

  1. org.eclipse.jetty.webapp.WebAppContext: Failed startup of context o.e.j.w.WebAppContext@7e0b0338{/,file:///var/lib/jetty/webapps/root/,UNAVAILABLE}{/root.war}

型
另外，以下是相关文件：
app.yaml:

  1. runtime: java
  2. env: flex
  4. runtime_config:  # Optional
  5.   jdk: openjdk8
  7. service: service2
  9. handlers:
  10. - url: /.*
  11.   script: this field is required, but ignored
  13. manual_scaling:
  14.   instances: 1

型
build.gradle:

  1. buildscript {      // Configuration for building
  2.     ext {
  3.         springBootVersion = '1.5.9.RELEASE'
  4.     }
  5.     repositories {
  6.         jcenter()      // Bintray's repository - a fast Maven Central mirror & more
  7.         mavenCentral()
  8.         maven { url 'https://repo.spring.io/libs-snapshot' }
  9.     }
  10.     dependencies {
  11.         classpath 'com.google.cloud.tools:appengine-gradle-plugin:+'
  12.         classpath "org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}"
  13.     }
  14. }
  16. repositories {   // repositories for JARs you access in your code
  17.     maven {
  18.         url 'https://maven-central.storage.googleapis.com'             // Google's mirror of Maven Central
  19.     }
  21.     maven {
  22.         url "http://repo.spring.io/libs-snapshot"
  23.     }
  25.     jcenter()
  26.     mavenCentral()
  27. }
  29. apply plugin: 'java'
  30. apply plugin: 'war'
  31. apply plugin: 'com.google.cloud.tools.appengine'
  32. apply plugin: 'org.springframework.boot'
  34. dependencies {
  36.     // Add your dependencies here.
  37.     compile "org.springframework.boot:spring-boot-starter-web", { exclude group: 'org.springframework.boot', module: 'spring-boot-starter-tomcat' }
  38.     compile (
  39.             "org.springframework.boot:spring-boot-starter-actuator",
  40.             "org.springframework.boot:spring-boot-starter-jetty"
  41.     )
  42.     testCompile (
  43.             "org.springframework.boot:spring-boot-starter-test:$springBootVersion"
  44.     )
  46. }
  48. appengine {
  50.     deploy {   // deploy configuration
  51.         stopPreviousVersion = true  // default - stop the current version
  52.         promote = true              // default - & make this the current version
  53.     }
  55. }
  57. group = 'com.example'   // Generated output GroupId
  58. version = '1.0-SNAPSHOT'          // Version in generated output
  60. sourceCompatibility = 1.8
  61. targetCompatibility = 1.8

型
HelloworldApplication.java:

  1. package com.example.java.gettingstarted;
  3. import org.springframework.boot.SpringApplication;
  4. import org.springframework.boot.autoconfigure.SpringBootApplication;
  5. import org.springframework.web.bind.annotation.RequestMapping;
  6. import org.springframework.web.bind.annotation.RestController;
  8. @SpringBootApplication
  9. @RestController
  10. public class HelloworldApplication {
  11.   @RequestMapping("/service2/")
  12.   public String home() {
  13.     return "Helloooooooo Nurse!";
  14.   }
  16.   /**
  17.    * (Optional) App Engine health check endpoint mapping.
  18.    * @see <a href="https://cloud.google.com/appengine/docs/flexible/java/how-instances-are-managed#health_checking"></a>
  19.    * If your app does not handle health checks, a HTTP 404 response is interpreted
  20.    *     as a successful reply.
  21.    */
  22.   @RequestMapping("/_ah/health")
  23.   public String healthy() {
  24.     // Message body required though ignored
  25.     return "Still surviving.";
  26.   }
  28.   public static void main(String[] args) {
  29.     SpringApplication.run(HelloworldApplication.class, args);
  30.   }
  31. }

型
我也运行gcloud版本184.0.0

spring-boot

1条答案

按热度按时间
j5fpnvbx

j5fpnvbx1#

这个解决方案最终有点神奇，但SpringBoot documentation告诉我，一旦appengine标准文档为我指出了正确的方向。
请注意，只有在构建并部署war文件时才需要WebApplicationInitializer。如果您更喜欢运行嵌入式容器，则根本不需要它。
我们正在部署一个war，它在本地使用嵌入式容器运行。在按照提供的方式设置jetty并将神奇的SpringBootServletInitializer添加到根目录后，事情就开始工作了。我不知道为什么两周前不需要它，但现在肯定需要它。

  1. import org.springframework.boot.builder.SpringApplicationBuilder;
  2. import org.springframework.boot.web.support.SpringBootServletInitializer;
  4. public class ServletInitializer extends SpringBootServletInitializer {
  5.     @Override
  6.     protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
  7.         System.out.println("ServletInitializer called.");
  8.         return application.sources(HelloworldApplication.class);
  9.     }
  10. }

字符串
把这个文件放在根目录下就可以了。
谢谢你的帮助

展开查看全部
赞(0）分享  回复(0）举报  2023-11-17
我来回答

相关问题

    查看更多

    热门标签

    更多
    JavaquerypythonNode开发语言requestUtil数据库Table后端算法LoggerMessageElementParser

    最新问答

    更多
    • 蜀ICP备13028337号-1 大数据知识库 https://www.saoniuhuo.com © All rights reserved
    • 本站内容来源互联网,如果侵犯您的权益请联系我们删除, 联系方式：448109455@qq.com