I deployed a simple app to test it, I've succeeded in deploying it and it runs normally. But When I try accessing it responds with 404.
After I run it
When I try to access http://<MY_IP>:8888/ or http://<MY_IP>:8888/cayan, I get
Am I missing something?
Thanks & Appreciate your kind help.
Related
I have simple micronaut application which has below one end point
test/g1
which returns some string.
I created the the fat jar and deployed same on PCF(pivotal cloud foundry).
The application is in running state but I am not able to access the endpoint.
Got the the below error -
502 Bad Gateway: Registered endpoint failed to handle the request.
Any kind of help is much appreciated.
Please note same application is running properly when deployed on my local machine.
I am facing a weird issue in my project.
After a deployment of a particular service (myServices) in a remote server I am trying to open http://serverIp:port/myServices/ and I am getting 404.
Also, I tried to open a sample html (test.html) directly by hitting http://serverIp:port/myServices/test.html and then also I got same error. The location
of test.html is webapps\myServices\test.html.
I verified that the service is running in the correct port. In fact, while I am trying to hit that service from our application its working fine.
I am facing issue only if I try to hit that service direclty.
Please help me resolving this issue.
We are using Tomcat 8 and Java 1.8
Thanks.
The service(or the application) may not be bound to the public ip, it may just be bound to localhost and hence if the other application is also running on the same machine - it will not have any issues in calling the service.
I developed a very simple web service using eclipse for edit the code and tomcat 8.5 for deploy the web service. The Name of maven project is PruebaMaven and I can deploy that with success getting the classic hello world.
My problem is that when I want to access an a method associate to localhost:8080/PruebaMaven/Services/Login/Validate, the tomcat response is HTTP 404 - Not found
The method that I want to access is a POST type, so I'm expecting that the response of the tomcat server be a HTTP 405.
I dont know if my thinking is correct or im wrong and the response of tomcat is apropiate. In the case that my thinking is correct, somebody know where is my issue?
I am running a springboot application and I ran it two ways:
1) running the spring boot app within eclipse run as -> application and selecting the Application.java for the spring boot app and running it in Eclipse itself. All the POST requests I am sending to it work perfectly fine.
2) compile the spring boot into a jar and then run it as java -jar <>.jar. The application starts fine but only SOME of the POST requests work this time.
Is there a reason why this could be happening? I am not sending the requests differently in either case. In the second case, I am getting a 500 error
OK I figured out the issue, I have an angular frontend where I am passing in Typescript objects back to the server which Spring then automatically maps to POJOs. For some reason, this mapping was working when I ran the application in Eclipse as an Eclipse application, but not when I ran the packaged JAR as a standalone server.
This is the reason behind the error, but if anyone can shed light on WHY this difference in mapping exists, it would make this less painful.
I have with me the client interface for a web service that was built using JBoss/RESTeasy. The web service calls work fine when they are invoked from a stand-alone app, but as soon as I put them into a webapp running in a Tomcat container (on the same machine), they start behaving weirdly. Some of the calls return empty results while some others simply fail with this exception:
org.jboss.resteasy.client.ClientResponseFailure: Error status 404 Not Found returned
Any idea of what might be going on? Could this be a result of a library conflict? All the required client libraries are in the WEB-INF/lib directory of the webapp.
Seems that your services are not deployed properly. Take a look at your catalina.out or some other logs for more details.