tomcat successfully started alone, eclipse tomcat start being given the wrong one: Can not find or load the main class org.apache.catalina.startup.Bootstrap; Error two: port is occupied

For a successful start tomcat just met individually, but starts in the eclipse to tomcat error on the issues summarized as follows:

Software version:

  1. eclipse version

     ① Luna Service Release 2(4.4.2)    64位

     ② Helios Service Release 2   64位

  2. tomcat version

     ①apache-tomcat-6.0.14

     ②apache-tomcat-6.0.35

  3. JDK version

     jdk1.6.0_45 64 Wei

 Error details:

  1. tomcat failed to start, error:

       java.lang.ClassNotFoundException: org.apache.catalina.startup.Bootstrap

  2. For another version of the Eclipse startup error:

       8005,8080,8009 port is occupied, should add here, I checked the task manager, no extra process, also found no application using these ports

 Error investigation process:

  1. First check the jdk environment variable (no problem)

  2. eclipse jdk version and version match (both 64-bit no problem)

  3. Start tomcat services separately from the outside (no problem)

  4. Restart the gateway (or restart reported the same mistake, so excluded)

  5. tomcat service configuration CLasspath-> bootstrap.jar package references under User Entries (no problem)

  6. Create a version of tomcat tomcat service selection and tomcat version matches (no problem)

Final settlement of the success of the program:

  The Internet to find all kinds of eclipse tomcat start being given issue, what ports are occupied, can not find the main class, have been tried but have not been resolved, and finally I put part of the problem from the root cause analysis of the most

  1. First, eclipse, jdk, tomcat all with clean version (ie extracting from the archive, have not used before)

  2. Delete the environment variable reconstruction

  3. reconstruction work space

  4. eclipse again cited jdk, jre, reconfigure the tomcat service

 Again start tomcat actually successful, then I feel very magical, plagued by environmental problems a few days so resolved, after careful analysis, is there such a mistake because of my eclipse workspace different versions point to a directory, cause a version conflict occured, low version with a higher version of eclipse can not use the same workspace, thus finally solved the problem, special record here.

Guess you like

Origin www.cnblogs.com/MMPAnubis/p/11513145.html