The underlying issue was that Tomcat was installed in /opt/some-tomcat and required root privileges to start but Eclipse ran with my user privileges - which were not sufficient to start Tomcat. In the end (and after several re-installations of Eclipse and Tomcat), I stumbled across a permission problem that was only visible if I tried to define a new server when trying "Run as." without first having a Tomcat server or runtime defined. In my case, deleting the above mentioned files did not help. I also wrote about it on Stackoverflow (in reply to "Unable to run a jsp project in eclipse" - unfortunately, I cannot yet post URIs in the Eclipse forum due to low post count) but since I used this thread during my troubleshooting, I thought I post some information here as well: I just solved a similar problem (no existing Tomcat server despite having it defined, "Run as." points to manual definition on localhost but does not allow to define a new server) on a clean install of Eclipse Luna on Centos 7 with Tomcat 7 and JDK 1.7. Download of apache-tomcat-7.0.42.zip ( apache-tomcat-7.0.42.zip ( external link: SF.net): 17,191,690 bytes) will begin shortly. Should have been asked in the first place, someone there might want toĭo it for you since it's pretty important. This issue up in the Eclipse web tools forum, which is really where this You should go to the trouble of submitting a bug report. It), but I had no trouble creating a Tomcat 6 server in Kepler. I don't use 7 (just saying, not making a point of I found a Juno fix by removing some config files, but it did > I have attempted to remove the runtime and add it again with no > If I selected Tomcat v6.0 Server, the server host name is localhost and I executed these steps to create new Server in Eclipse: I have also experienced this problem with Eclipse Kepler running on
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |