Jetty Web服务器会自动在EC2上经常关闭



寻求帮助。Jetty 8.1.14.v20131031在EC2 Ubuntu 12.04上运行。它在启动后3小时内自动关闭。只是为了确认这不是我的代码问题,我从服务器中删除了战争文件,并从默认[spdy.war and test.war]开始,但是结果相同。3小时后,它被关闭了。Jetty不会在日志中记录任何错误。只是提到这个问题始于一个月前,在此之前运行良好。

这是日志 -

Web服务器启动 -

2016-11-28 18:00:30.694:INFO:oejs.Server:jetty-8.1.14.v20131031 2016-11-28     18:00:30.712:INFO:oejdp.ScanningAppProvider:Deployment monitor   /opt/jetty/webapps at interval 1 2016-11-28
18:00:30.718:INFO:oejd.DeploymentManager:Deployable added:  /opt/jetty/webapps/test.war 2016-11-28 18:00:30.748:INFO:oejw.WebInfConfiguration:Extract jar:file:/opt/jetty/webapps/test.war!/ to
/mnt/tmp/tmp/jetty-0.0.0.0-8080-test.war-_test-any-/webapp 2016-11-28 18:00:31.594:INFO:oejs.TransparentProxy:TransparentProxy @ /test/javadoc-proxy to http://download.eclipse.org/jetty/stable-
8/apidocs 2016-11-28 18:00:31.594:INFO:oejd.DeploymentManager:Deployable added: /opt/jetty/webapps/spdy.war 2016-11-28 18:00:31.596:INFO:oejw.WebInfConfiguration:Extract
jar:file:/opt/jetty/webapps/spdy.war!/ to /mnt/tmp/tmp/jetty-0.0.0.0-8080-spdy.war-_spdy-any-/webapp 2016-11-28 18:00:31.677:INFO:oejdp.ScanningAppProvider:Deployment monitor /opt/jetty/contexts at
interval 1 2016-11-28 18:00:31.678:INFO:oejd.DeploymentManager:Deployable added: /opt/jetty/contexts/javadoc.xml 2016-11-28 18:00:31.709:INFO:oejs.AbstractConnector:Started
SelectChannelConnector@0.0.0.0:8080

只是空闲。

之间没有登录

3小时后自动停止 -

2016-11-28 21:11:27.567:INFO:oejs.Server:Graceful shutdown SelectChannelConnector@0.0.0.0:8080 2016-11-28 21:11:27.567:INFO:oejs.Server:Graceful shutdown o.e.j.w.WebAppContext
{/test,file:/mnt/tmp/tmp/jetty-0.0.0.0-8080-test.war-_test-any-/webapp/},/opt/jetty/webapps/test.war 2016-11-28 21:11:27.568:INFO:oejs.Server:Graceful shutdown o.e.j.w.WebAppContext
{/spdy,file:/mnt/tmp/tmp/jetty-0.0.0.0-8080-spdy.war-_spdy-any-/webapp/},/opt/jetty/webapps/spdy.war 2016-11-28 21:11:27.568:INFO:oejs.Server:Graceful shutdown o.e.j.s.h.ContextHandler
{/javadoc,file:/opt/jetty/javadoc/} 2016-11-28 21:11:28.589:INFO:oejsh.ContextHandler:stopped o.e.j.s.h.ContextHandler{/javadoc,file:/opt/jetty/javadoc/} 2016-11-28
21:11:28.601:INFO:oejsl.ELContextCleaner:javax.el.BeanELResolver purged 2016-11-28 21:11:28.601:INFO:oejsh.ContextHandler:stopped o.e.j.w.WebAppContext{/spdy,file:/mnt/tmp/tmp/jetty-0.0.0.0-8080-
spdy.war-_spdy-any-/webapp/},/opt/jetty/webapps/spdy.war 2016-11-28 21:11:28.664:INFO:oejsl.ELContextCleaner:javax.el.BeanELResolver purged 2016-11-28 21:11:28.665:INFO:oejsh.ContextHandler:stopped
o.e.j.w.WebAppContext{/test,file:/mnt/tmp/tmp/jetty-0.0.0.0-8080-test.war-_test-any-/webapp/},/opt/jetty/webapps/test.war

注意:Jetty 8是EOL(生命的尽头),请考虑升级。

这个问题并不是真正适合Stackoverflow,因为它不是编程问题。

这个问题将在ServerFault的amazon-web-services标签上更适合。

2016-11-28 21:11:27.567:INFO:oejs.Server:Graceful shutdown表示某人(或码头之外的某个过程)专门告诉它关闭。

这不是偶然的,也不是码头决定自己关闭,看着码头外面寻找答案。(服务配置,CRON,AWS配置,其他用户等)

我开始忽略吊架信号的码头,而目前这项工作似乎在起作用。我使用此命令[nohup java -jar start.jar&]开始了码头。但是关闭信号的根本原因仍然远离我的视线。

相关内容

  • 没有找到相关文章

最新更新