[英]AWS ELB: Failed to load resource: the server responded with a status of 503 (Service Unavailable: Back-end server is at capacity)
my cloudformation stack is deployed successfully. 我的cloudformation堆栈已成功部署。 I'm trying to deploy a clojure ring app on EC2.
我正在尝试在EC2上部署Clojure Ring App。
When I access my elastic load balance endpoint at my-app.us-west-1.elb.amazonaws.com
I get Failed to load resource: the server responded with a status of 503 (Service Unavailable: Back-end server is at capacity)
当我访问位于
my-app.us-west-1.elb.amazonaws.com
弹性负载平衡终结点时,我Failed to load resource: the server responded with a status of 503 (Service Unavailable: Back-end server is at capacity)
my-app.us-west-1.elb.amazonaws.com
Failed to load resource: the server responded with a status of 503 (Service Unavailable: Back-end server is at capacity)
I confirmed the tomcat was running by sshing into the ec2 and running ps -afx
我通过插入ec2并运行
ps -afx
确认tomcat正在运行
So what could possibly be the problem here? 那么这里可能是什么问题呢?
update: okay so doing a curl request to localhost:8080 returns HTTP 500 更新:好的,因此向本地主机执行卷曲请求:8080返回HTTP 500
SEVERE: Servlet.service() for servlet [clj-west.system/servlet-handler servlet] in context with path [] threw exception
java.lang.NullPointerException: Handler returned nil
at ring.util.servlet$make_service_method$fn__52.invoke(servlet.clj:127)
at clj_west.servlet$_service.invoke(servlet.clj:1)
at clj_west.servlet.service(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1078)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Based on the discussion from comments. 基于评论的讨论。 The issue got resolved by updating the healthcheck on the ELB.
通过更新ELB上的运行状况检查,此问题已解决。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.