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.
Related
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.
I'm new to JavaEE and just started using eclipse with weblogic server,
whenever i try open localhost page in internal webbrowser, it gives Error 404, even i'm not able to execute hello world program in eclipse, please help me how to resolve this problem.
thanks in advance.
We're currently running on App Engine (Java) and want to test the new managed VMs that Google are beta testing.
Everything builds, but I can't get any of the endpoints to work.
When I build, the error that comes back is:
SEVERE: Endpoints configuration not updated. The app returned an
error when the Google Cloud Endpoints server attempted to communicate
with it.
In the admin logs I can see that it has attempted, but the error comes back:
API configuration update failed
The discovery docs get created locally, but there isn't anything in the logs.
I can see the POST to the getApiConfigs, but no details on the failure.
Hopefully someone else has encountered the same problem and can help?
In essence my question is, what do I need to do to get cloud endpoints running on a managed VM for App Engine?
Thanks
Have you checked your logs at https://console.cloud.google.com/logs/viewer ?
I had the same problem and after checking the logs I realized that I had two classes with the same API name and version but one had namespace and the other didn't.
All API classes with the same API name and version must have the exact same API-wide configuration.
I just set the namespace to be the same for both API's and it worked.
I have recently downloading Tomcat 6 and switch the eclipse I was using to the EE edition.I am having trouble getting eclipse to run the JPA project, and I keeping getting the error message HTTP 404. When I open a web browser and type in http://localhost/8080/ I get the tomcat 6 info page so I think the server does work eclipse cannot connect to it.
I have going into the preferences and and made sure the path to the server in the directory was correct..
If you're using "your own" instance of tomcat you must specify the location in the server configuration view. Take a look at the screenshot :
My instance is located at C:\TOMCT. Hope that helps
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.