堆栈内存溢出
  简体   繁体   English

AWS Elastic Beanstalk：Tomcat 忽略我的 WAR 文件

[英]AWS Elastic Beanstalk: Tomcat ignoring my WAR-File

 原文  2016-09-23 14:35:55  8   2    java/ spring/ amazon-web-services/ tomcat/ amazon-elastic-beanstalk

问题描述

i'm trying to get my Spring Boot Application into AWS-EB and I already succeeded yesterday using Java as my Platform.我正在尝试将我的 Spring Boot 应用程序放入 AWS-EB，昨天我已经成功使用 Java 作为我的平台。 However having Tomcat as Platform in EB allows me to configure platform-specific properties (database etc) directly in my AWS-Console so I created a new environment with Tomcat as the underlying platform.但是，在 EB 中将 Tomcat 作为平台允许我直接在我的 AWS 控制台中配置特定于平台的属性（数据库等），因此我创建了一个以 Tomcat 作为底层平台的新环境。 Now I deployed my WAR-File (that worked yesterday with plain java) and the tomcat is completely ignoring me :( See the log attached below. I don't see an error-message anywhere it just boots up but does not deploy the WAR-File anywhere. Does anyone have an idea what I'm missing? I haven't found anyone having the same problem.现在我部署了我的 WAR 文件（昨天使用纯 Java 工作），而 tomcat 完全无视我 :( 请参阅下面附上的日志。我在它启动但未部署 WAR 的任何地方都没有看到错误消息- 随处归档。有人知道我缺少什么吗？我没有发现任何人有同样的问题。

Thanks in advance!提前致谢！ :) :)

Catalina.out卡特琳娜.out

23-Sep-2016 13:20:34.889 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.0.36
23-Sep-2016 13:20:34.892 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Aug 12 2016 18:14:42 UTC
23-Sep-2016 13:20:34.892 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.0.36.0
23-Sep-2016 13:20:34.892 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
23-Sep-2016 13:20:34.892 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            4.4.16-27.56.amzn1.x86_64
23-Sep-2016 13:20:34.892 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
23-Sep-2016 13:20:34.893 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.101-3.b13.24.amzn1.x86_64/jre
23-Sep-2016 13:20:34.897 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_101-b13
23-Sep-2016 13:20:34.901 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
23-Sep-2016 13:20:34.901 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /usr/share/tomcat8
23-Sep-2016 13:20:34.901 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /usr/share/tomcat8
23-Sep-2016 13:20:34.902 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dspring.datasource.username=USERNAME
23-Sep-2016 13:20:34.903 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -DPORT=8080
23-Sep-2016 13:20:34.903 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dspring.datasource.url=DATABASE_URL
23-Sep-2016 13:20:34.903 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -DJDBC_CONNECTION_STRING=
23-Sep-2016 13:20:34.903 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dspring.datasource.password=PASS
23-Sep-2016 13:20:34.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms256m
23-Sep-2016 13:20:34.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx256m
23-Sep-2016 13:20:34.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=64m
23-Sep-2016 13:20:34.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/usr/share/tomcat8
23-Sep-2016 13:20:34.904 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/usr/share/tomcat8
23-Sep-2016 13:20:34.905 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
23-Sep-2016 13:20:34.906 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=
23-Sep-2016 13:20:34.906 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/var/cache/tomcat8/temp
23-Sep-2016 13:20:34.906 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/usr/share/tomcat8/conf/logging.properties
23-Sep-2016 13:20:34.906 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
23-Sep-2016 13:20:34.906 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
23-Sep-2016 13:20:35.119 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
23-Sep-2016 13:20:35.162 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
23-Sep-2016 13:20:35.174 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
23-Sep-2016 13:20:35.176 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
23-Sep-2016 13:20:35.181 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1218 ms
23-Sep-2016 13:20:35.237 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
23-Sep-2016 13:20:35.237 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.36
23-Sep-2016 13:20:35.261 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /var/lib/tomcat8/webapps/ROOT
23-Sep-2016 13:20:38.313 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
23-Sep-2016 13:20:38.362 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /var/lib/tomcat8/webapps/ROOT has finished in 3,101 ms
23-Sep-2016 13:20:38.368 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
23-Sep-2016 13:20:38.377 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
23-Sep-2016 13:20:38.377 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 3196 ms

Screenshot from my config:我的配置截图：

在此处输入图片说明

2 个解决方案

解决方案1
 0  2016-09-23 16:14:01

Read http://tomcat.apache.org/native-doc/ , then download from http://tomcat.apache.org/download-native.cgi阅读http://tomcat.apache.org/native-doc/ ，然后从http://tomcat.apache.org/download-native.cgi下载

then put to where Tomcat expected:然后放到 Tomcat 期望的位置：

the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

解决方案2
 0 已采纳  2016-09-26 13:01:41

I solved it by using the normal Java Platform in EB and parsing an environment-variable to a JVM arg, before I start my spring-server.在启动 spring-server 之前，我通过在 EB 中使用普通的 Java 平台并将环境变量解析为 JVM arg 来解决它。

Here's the code for the Spring Boot-App这是 Spring Boot-App 的代码

public class EnvironmentVariableParser {
    private static final Log log = LogFactory.getLog(EnvironmentVariableParser.class);

    public static void appendArguments() {
        final String customJvmArgs = System.getenv().get("CUSTOM_JVM_ARGS");
        if (customJvmArgs == null) {
            return;
        }

        for (String entry : customJvmArgs.split(" ")) {
            log.info(String.format("found custom jvm arg for: %s", entry));
            final int separator = entry.indexOf('=');
            System.setProperty(entry.substring(0, separator), entry.substring(separator + 1, entry.length()));
        }
    }
}

After that you can just call it, before you start your Application之后，您可以在启动应用程序之前调用它

public static void main(String[] args) {
        EnvironmentVariableParser.appendArguments();
        SpringApplication.run(MyServerApplication.class, args);
}

Then you can just specify "CUSTOM_JVM_ARGS" as an environment-variable and paste in your properties (seperated by spaces).然后您可以将“CUSTOM_JVM_ARGS”指定为环境变量并粘贴到您的属性中（以空格分隔）。 Not the prettiest thing ever, but it works.. :P不是有史以来最漂亮的东西，但它有效..：P

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 将现有的 java WAR 文件上传到 AWS Elastic Beanstalk - Upload existing java WAR file to AWS Elastic Beanstalk 在 AWS Beanstalk 中运行 WAR 文件 - Run WAR file in AWS Beanstalk AWS Elastic Beanstalk Tomcat - 高内存使用率 - AWS Elastic Beanstalk Tomcat - high memory usage Elastic Beanstalk Servlet过滤器上的AWS Tomcat - AWS Tomcat on Elastic Beanstalk servlet Filter 弹力豆茎 | CodePipeline 将无法正确部署 .war 文件 - Elastic Beanstalk | CodePipeline will not deploy .war file correctly 在Elastic Beanstalk上更改Apache Tomcat的文件编码 - Change File Encoding of Apache Tomcat on Elastic Beanstalk Spring AWS：在Elastic Beanstalk上部署War时访问被拒绝错误 - Spring AWS: Access denied error when deploying war on Elastic Beanstalk 如何将Spring Boot应用程序大战部署到AWS Elastic Beanstalk？ - How to deploy Spring Boot application war to AWS Elastic Beanstalk? AWS Elastic Beanstalk SpringBoot 胖 WAR：未找到 jsp - AWS Elastic Beanstalk SpringBoot fat WAR : jsp not found 使用共享资源部署战争文件 - War-file deployment with shared resources
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM