1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
I would be looking closer at your applicaiton. Perhaps the web server is too busy to respond to requests, perhaps you have a threading issues where it has run out of threads
Just because the CPU is fine, you may stil have some performance tuning of your applicaiton/underlying listeners in your container to perform. I would ensure your application is sending enough log information to review and you could even test connecting directly to your application when you experience the 503 errors.
You could connect into the container also during the time it has issues if its logging locally
If this answers your question, please be sure to accept so that this helps others and helps me
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 일 년 전
Hi @Gary Mclean, Thanks for your inputs, the 503 was some aws outage is not happening since then. Also we use threading and the API handles multiple request without a challenge. However, we still are getting Error Status Code 0 in our app, wondering how the Name is Resolved other times expect very few (maybe 2-3 time a day). This is quite puzzling.