java - ERROR: Running application failed - Spring boot + Boxfuse/AWS -
i trying run spring boot application on aws using boxfuse. have followed following tutorial spring (section 54.4) , get started boxfuse aswell.
when run following command
boxfuse run target\digigram-0.1.0.jar -env=prod
i following lines
waiting aws boot instance i-74fe7fc8 , payload start @ http://52.28.94.159:8080/ ... warning: healthcheck (http://52.28.94.159:8080/) returned 404 instead of 200. retrying next 120 seconds ... terminating instance i-74fe7fc8 ...
and ends with
destroying security group sg-0ed6f667 ... error: deployment of pantera160/digigram:0.0.0.1453900589995 failed in prod:payload of instance i-74fe7fc8 came @ http://52.28.94.159:8080/ http 404 (expected 200) => ensure application responds http 200 @ http://52.28.94.159:8080/ or adjust healthcheck configuration (healthcheck.path, healthcheck.timeout, ...) fit application error: running pantera160/digigram:0.0.0.1453900589995 failed!
i don't understand problem lies. have change in aws or in application or...
any appreciated.
note:
running on free plan aws, might problem?
boxfuse ensures correct version of app stays , running , not replaced bad one. when new version pass boxfuse's health check, boxfuse reassign application's elastic ip. once complete boxfuse terminates instance of old version.
to verify new version of app comes correctly boxfuse expects new version's instance's healthcheck path return http 200.
the default healthcheck path regular spring boot application without actuator /
. app answers 404 there instead of 200.
you have number of options fix this:
- add controller app mapped
/
returns http 200 when app comes correctly. - change boxfuse's
healthcheck.path
different path indeed answer http 200 when app comes correctly. - disable boxfuse's health checks setting
healthcheck
false
(not recommended prevents boxfuse checking whether application came correctly)
pick either 1 of these options , app come correctly expect.
Comments
Post a Comment