Eclipse – Tomcat not starting from eclipse

eclipsetomcat

I'm trying to start tomcat server 6.0.32 (NOT MY APP) from eclipse but it fails with error "Server Apache Tomcat v6.0.32 at localhost failed to start". But when I'm starting it with startup.bat it is ok. I checked all ports for tomcat – they are free. Here it is a console log

11.08.2011 15:15:46 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: <MY_PATH_VARIABLE>
11.08.2011 15:15:47 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
11.08.2011 15:15:47 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1068 ms
11.08.2011 15:15:47 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
11.08.2011 15:15:47 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
11.08.2011 15:15:47 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ProjectName.xml

Maybe someone know how to fix it?((((

Best Answer

I had the same problem i.e. no errors in any of the logs, and the server started fine when launched from the command line using run.sh. However as soon as I used Eclipse (without or without my app) Tomcat wouldn't start at all.

I solved this problem by performing the following steps:

In Eclipse, go to the 'Servers' tab.
Double click the server.
A configuration overview should be displayed in the main Eclipse panel.
Under the sub-section 'Server Locations', select the radio button 'Use Tomcat Installation' (for me this was the middle radio button).
Save the configuration (you should be prompted to do so anyway).
Restart your server, and you should find localhost:8080 works from within the Eclipse browser.

Related Solutions

Eclipse – How to you speed up Eclipse

The three most influential factors for Eclipse speed are:

Using the latest version of Eclipse (2020-06 as on 26 June 2020)
Note that David Balažic's comment (July 2014) contradicts that criteria which was working six years ago:

The "same" workspace in Indigo (3.7.2) SR2 loads in 4 seconds, in Kepler SR2 (4.3.2) in 7 seconds and in Luna (4.4.0) in 10 seconds. All are Java EE bundles. Newer versions have more bundled plugins, but still the trend is obvious. (by "same" workspace I mean: same (additionally installed) plugins used, same projects checked out from version control).

Launching it with the latest JDK (Java 14 at the time of writing, which does not prevent you to compile in your Eclipse project with any other JDK you want: 1.4.2, 1.5, 1.6 older...)
```
  -vm jdk1.6.0_10\jre\bin\client\jvm.dll
```
Configuring the eclipse.ini (see this question for a complete eclipse.ini)
```
  -Xms512m
  -Xmx4096m
  [...]
```

The Xmx argument is the amount of memory Eclipse will get (in simple terms). With -Xmx4g, it gets 4 GB of RAM, etc.

Note:

Referring to the jvm.dll has advantages:

Splash screen coming up sooner.
Eclipse.exe in the process list instead of java.exe.
Firewalls: Eclipse wants access to the Internet instead of Java.
Window management branding issues, especially on Windows and Mac.

Dec. 2020, Udo conforms in the comments

From version 4.8 (Photon) an up there was a steady speed gain after each version.
The main platform was optimized every release to load faster, enable more features for the dark theme and to add more features for newer Java versions for the Java development tools.
Especially with-in the last 3 versions the startup time was increased a lot. There should be a significant increase in start-up time with the newest version of Eclipse 2020-12.

In my experience it started a lot faster with each new version.
But: There are still plug-ins which do not follow the new way of using the Eclipse API and are therefore still slow to start.
Since the change to Java 11 as the minimum runtime version starting from Eclipse version 2020-09 at least the core system uses the newer features of the JVM. It is up to the providers of the other plug-ins to upgrade to newer APIs and to use the full power of modern CPUs (e.g. concurrent programming model).

Java – trying to start a tomcat from eclipse and it failed to find index.jsp

If you're using Eclipse 3.4 or 3.5 -- look at the Servers view in Eclipse. Against your server, you should see "Started" and "Synchronized". If it tells you to restart or republish, right-click on your server and do so.

Deploy your file again (you can drag your index.jsp file on to the server). Does it start this time?

If not, something could be wrong with your web.xml. Open the Console view and look at the server log -- do you notice any exceptions etc? You will need to resolve those.

Best Answer

Related Solutions

Eclipse – How to you speed up Eclipse

Java – trying to start a tomcat from eclipse and it failed to find index.jsp

Related Topic