Meaningless Drivel is fun!*
The moose likes Tomcat and the fly likes http://localhost:8080 stopped responding Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "http://localhost:8080 stopped responding" Watch "http://localhost:8080 stopped responding" New topic
Author

http://localhost:8080 stopped responding

Nitin Nigam
Ranch Hand

Joined: Jul 03, 2006
Posts: 129
Hi all,
I had my Tomcat running fine at localhost:8080 so did some applications that i had deployed on it. Last week i installed an application(say 'A') that uses jetty server on port 8364. Since then http://localhost:8000 is not responding, and all the applications i deployed on tomcat have also stopped responding.

Is it like when you have another server running (on different port) tomcat wont run on the same machine?
I noticed another thing, the application that installed jetty server had also changed my class path, now this classpath points to location where my application 'A' had installed another JDK. And all the previous entries of the classpath are gone.

So i put the path to CATELINA_HOME/common/lib (here are all my jar files located) to my classpath. Still my application deployed on tomcat are not responding. Even http://localhost:8080 is not responding.

Can anybody indicate whats wrong with my Tomcat? Is there anything else i need to put in classpath?
[ April 04, 2007: Message edited by: Nitin Nigam ]

Nothing is impossible; for those who doesnt have to do it themselves.
myjotting.blogspot.com
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12681
    
    5
>>Is it like when you have another server running (on different port) tomcat wont run on the same machine?

As long as the ports used by both are all separate there should be no problem. NOTE that in addition to 8080 Tomcat watches a "SHUTDOWN" port - see your server.xml file

I noticed another thing, the application that installed jetty server had also changed my class path, now this classpath points to location where my application 'A' had installed another JDK. And all the previous entries of the classpath are gone.

So i put the path to CATELINA_HOME/common/lib (here are all my jar files located) to my classpath. Still my application deployed on tomcat are not responding.


Tomcat totally ignores your classpath settings to avoid problem like your installation that changed CLASSPATH but does look at environment variables for JAVA_HOME and CATALINA_HOME - what do your present values look like?

What method are you using to start Tomcat? Can you see the running java instance in Task Manager?

Bill


Java Resources at www.wbrogden.com
Nitin Nigam
Ranch Hand

Joined: Jul 03, 2006
Posts: 129
Hi BIll,
Thanks for the reply.
I am using the My Computer(Right-Click)-> Manage->Services to restart tomcat.
I have JAVA_HOME and CATELINA _HOME properly defined.
My server.xml has nothing about shutdown port.
I have my Eclipse running, so javaw.exe is visible in Task Manager. Also when i start tomcat, i can also see tomcat5.exe running in Task Manager.
[ April 05, 2007: Message edited by: Nitin Nigam ]
Ben Souther
Sheriff

Joined: Dec 11, 2004
Posts: 13410

Originally posted by Nitin Nigam:

I am using the My Computer(Right-Click)-> Manage->Services to restart tomcat.


When started this way (or as a Windows service) Tomcat doesn't use environment variables. The .exe installer stores these settings in the Windows Registry.

I'm guessing (as William mentioned) that there is a port conflict.
Look at server.xml and make sure the shutdown port:
<Server port="8005" shutdown="SHUTDOWN">
is not also being used by Jetty.

A simple test is to shut down Jetty and see if Tomcat will start.


Java API J2EE API Servlet Spec JSP Spec How to ask a question... Simple Servlet Examples jsonf
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12681
    
    5
When wrestling with a Tomcat problem, I find it best to start Tomcat from a command prompt window with startup.bat - that way you should be able to see a variety of imformative messages. The problem may become painfully obvious.

Bill
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: http://localhost:8080 stopped responding
 
Similar Threads
Debugging Eclipse
Apache -> Tomcat servlet problem
Beginning J2EE. Cannot reach deployed EAR.
Tomcat not Responding!!
Beginning J2EE. Cannot reach deployed EAR.