One of the property is not working when deployed with Openshift configmap, whereas it is working fine when deployed with application.properties
That property is a URL, which is working fine when deployed using appication.properties, where as it is throwing 401 error when we used with configmap.
Related
I have a springboot app which has 3 actuators enabled as below out of which 3rd one is custom,
application.properties code snippet
management.endpoints.web.exposure.include=health,refresh,customEndpoint
the endpoints when hit from local are working correctly. For example:-
http://localhost:8081/MyAppName/system/health gives below expected details:-
but when we hit the same endpoint(with pcf app route mapped) which is my_route_url/MyAppName/system/health, after deploying the app to pcf, it gives below 404 error:-
404 Not Found: Requested route ('my_route_url') does not exist.
Tried redeploying the app to pcf but that did not help.
Tried looking for solutions in other questions posted here but they are not matching scenario.
it's working in a different pcf foundation though.
I have a Springboot project and it has a api which I can invoke from postman.
When I run the application using Main Class I'm able to hit the endpoint and get response.
But if I deploy it on tomcat using war of project the same endpoint says 404!
What am I missing?
There can be multiple possibilities
You didn't extended your application class to SpringBootServletInitializer. In this case, spring boot application will not be deployed to tomcat. To fix this add "extends SpringBootServletInitializer" to your main application class
You are hitting wrong url. Make sure you append your aplication name to url. Example - if http://localhost:8080/data works in your local, and your application name is app, you have to hit http://{{serverip:port}}/app/data when deployed
There is something wrong in application properties like DB configured is local and not accessible from tomcat etc. To check such issues, check your tomcat log file (/{{tomcat dir}}/logs/catalina.out
The backend can be deployed but API call is not working.
The frontend project and backend project are separated, I am trying to deploy the backend(Spring Boot) project onto AWS Beanstalk using sub-generator and everything looks fine:
I have configured the server port to 5000 Deploying a Spring Boot Application on AWS Using AWS Elastic Beanstalk
When I invoke API with Beanstalk Environment URL, it always give me 404 Not Found error.
Does anyone know how to solve this issue?
I would like to host one application on AWS elastic beanstalk(java). The application has one view and one rest service. First I uploaded the jar file and tried accessing, the path to view was giving me whitelabel error on AWS but it is working fine locally. Also, am able to access the rest service with jar.
After surfing the net, I created a war and uploaded on AWS(tomcat). Now, the view is working fine but I notice the path of rest service is returning 404. Can someone suggest what should I check or do?
My colleague and me developed simple spring boot application and deployed (war file) in AWS Beanstalk. It is not worked properly.My first
page(loginpage.jsp-Get mapping) loaded perfectly in AWS. After submitting credentials my second page(Mainpage.jsp - Post mapping)
does not loaded. It shows internal server error=500 only. But we deployed on Tomcat server(local) all pages (Request and Response) loaded perfectly.
we did not added any cloud dependency in Pom.xml. Please help us...
This is our
Error message.
This is our
Pom.xml.