我们正在部署的弹性魔豆Java Web应用程序。默认情况下，魔豆提供了Tomcat7和放大器红帽情况; OpenJDK的。但我想自定义的情况下，这样我可以使用Sunjdk。  随后的步骤提到的here,我公司推出的EC2和放一个新的实例;安装了Sun JDK，tomcat7和创建实例的自定义AMI和青苗提供了其在自定义AMI ID字段ID在编辑环境配置。但我的环境，健康状态会变为红色，并且应用程序未部署。能否请你建议我解决这一点。

We are deploying a java web application in Elastic Beanstalk. The Beanstalk by default provides Redhat instances with Tomcat7 & openjdk. But i want to customize the instances so that i can use Sunjdk. Followed the steps as mentioned here, I launched a new instance from EC2 & installed sun jdk, tomcat7 and created a custom AMI of the instance and provided its ID in Custom AMI id field in edit Environment configuration in BeanStalk. But my Environment Health status is changing to RED, and the application is not deployed. Can you please suggest me a solution for this.

推荐答案

我有你想要做什么，并很高兴地报告，它的工作原理所做的正是。在我第一次尝试我遇到了同样的问题。请确保您：

I have done exactly what you want to do, and am happy to report that it works. In my first attempts I encountered the same issue. Make sure that you:

从亚马逊的豆茎AMI，您的的运行实例创建自定义AMI从EC2手动启动，而不是一个一个从通过魔豆开始你的应用程序中启动。这是非常重要的，因为闪烁着豆茎推出的EC2实例将无法正常工作！ 在安装Sun公司的Java按照这些指示，以确保所有的环境和符号链接都是正确的。 https://forums.aws.amazon.com/message.jspa?messageID=251168#251168 在耐心等待，因为我发现由于某种原因Tomcat的需要更长的时间来旋转起来比默认的OpenJDK配置。 Create your custom AMI from a running instance of Amazon's beanstalk AMI that you manually launch from EC2, NOT one that was launched from starting your application through beanstalk. This is very important, as Flashing a beanstalk launched EC2 instance won't work!! install Sun's Java as per these instructions, to make sure all the environment and symbolic links are correct. https://forums.aws.amazon.com/message.jspa?messageID=251168#251168 be patient, as I found for some reason Tomcat takes longer to spin up than with the default OpenJDK config.

如果您仍然无法得到它，请务必检查日志中/opt/tomcat7/logs/catalina.out - 我打了一个神秘的VerifyException，是由上传新的.jar环境解决，我也跑出PermGen的空间几乎立即，这是由魔豆编辑配置的容器配置区域加大了数值解决。

If you still can't get it, make sure you check the logs in /opt/tomcat7/logs/catalina.out - I hit a mysterious VerifyException that was resolved by uploading a new .jar to the environment, and I also ran out of permgen space almost immediately, which was resolved by upping the values in the 'Container' configuration area of the beanstalk 'edit configuration'.