404 error in eclipse - java

http://localhost:8081/
HTTP Status 404 - /
type Status report
message /
description The requested resource (/) is not available.
Apache Tomcat/6.0.32
in eclipse to start the server then server is started but i open the tomacat home page then show above error
please help.. me....

Given you're getting a 404 I'd hazard a guess you are indeed running on port 8081. So the message is what it says: the resource is not available. Tomcat applications often run with a "context" to separate them from other apps running in the same container. The context is just a path like /myapp or something. This should be configured in your web.xml.
So having checked the context is "/" do you actually have a file/resource bound to the root like an index page?
And last suggestion is: what's been printed out to the eclipse console? Any Exceptions? If the webapp did not start properly you will get a "resource not found"

Related

When I run Tomcat, the browser shows this error even though the HTML page is written correctly

HTTP Status 404 – Не найдено
Type Status Report
Message The requested resource [/] is not available
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/9.0.71
I cleared the cache of the browser
I opened and reinstalled Tomcat
Even if I close and open old projects and open new ones
enter image description here

Running Tomcat8 server Ubuntu 15.10

Started a Tomcat server. It is running and listening on port 8080 as seen in the image but the page http://localhost:8080 doesn't load. No Error page is seen. Just a blank screen. What could be the issue?
After I had installed Tomcat8, I checked and I was able to access the index page. Since then I have added a Java Servlet class file in WEB-INF/classes/com/example/web.
See the image for more details:
what link fails? but i believe that you fails in this, the tomcat index is 404 error the manager is in 8080/manager and the apps 8080/apps but 8080/ is 404 error

WebSphere Issue

I working in an Java application. I am using Struts2 and Hibernate. The application was working fine in Tomcat7 , But when I deployed that On IBM"S Websphere I am getting the following error for the following URL
http://localhost:8080/MYAPPS
Error 404: There is no Action mapped for action name .
http://localhost:8080/MYAPPS/
Error 404: There is no Action mapped for namespace [/] and action name [] associated with context path
The default port is 9080. Change the port in url as others suggested.
Check the following:
Login to the console , click on servers -> serverName -> ports -> WC_defaulthost (webcontainer port )
For example if it shows as 9080
Click on Environment -> Virtual Host -> default host (or the host the application is mapped to)- > Click on Host Aliases . Make sure the port is defined, if not add the port and the restart the server.
access the application as follow.
http://localhost:9080/MYAPPS/
http://hostname:9080/MYAPPS/
If the problem persists, open the systemout.log file and look for more details.
Try this, it may help to find the port number for web host or secure web host,
Go for the following path,
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01_demo/config/cells/localhostCell01/nodes/Dmgr_node,
try find this file serverindex.xml,
there you can find the "WC_adminhost" port number.
Hope this help !
thanks!.
I don't think this is the virtual host issue. You obviously have configured it right as there's no virtualhost error.
What's your WAS's version? WAS V6.1.X has the notorious reputation not to support whatever is popular. Try adding this as a customized web container property:
com.ibm.ws.webcontainer.invokefilterscompatibility
set its value to true

Logs for debugging a GAE app

I've deployed an application to GAE and now I get "404 NOT_FOUND" error.
Where I can find out the detailed information about this error (stack trace) ?
In "Logs" and "Admin logs" I didn't find anything useful.
Note: By "logs" I do not mean logs for site visiting statistics.
Update: Now I managed to get rid of the 404 error. However, now I get another logging related error:
[s~project-control-center/1.352785038340247795].:
Failed to instantiate [ch.qos.logback.classic.LoggerContext]
How can I fix it?
There have been some problems recently with displaying the logs in the admin console. You can try downloading the logs:
Log Download Docs
Set --severity=0 to get the DEBUG level.
All requests are logged, but the default view is to show only logs with error messages. Click on 'Show: All requests' on the top of the logging page to show all requests.
There's unlikely to be a stacktrace for a 404 not found message, because no error occurred - the URL you attempted to fetch simply didn't exist.

Internal Server Error

I am getting an unusual error while running my application, just wondering if anyone has come across this before. I am using google protocol buffers, my servlet takes a request and tries to process it, I have the following code:
InputStream s = request.getInputStream();
AdRequest adRequest = AdRequest.parseFrom(s);
After executing the second line I get the error below in Myeclipse debugger:
Source not found for ApplicationFilterChain.internalDoFilter(ServletRequest, ServletResponse) line: 310
I am using Jboss app server. I get a HTTP Status-Code 500: Internal Server Error.
Does anyone have any suggestions/thoughts?
I have sorted out the problem. The protobuffers.jar file was not being included in my projects .war file, even though I had added the jar to my project MyEclipse was not including it. Upon following the path to the Jboss server and looking inside the .war I found out the jar was not there. After copying it over to Jboss/.../default/server/deploy/myproject.war/WEB-INF/lib directory the error has gone away and I am able to send a request to the servlet.
Thanks.
Regards.
I'd check your jboss logs server//log/server.log (assuming you've not configured it to be somewhere else), and you'll get a better description of the problem.
The internal server error simply means that an unhandled exception is getting passed up the filter chain.

Categories

Resources