Unable to add server to the moved workspace

Question

I have this workspace downloaded from the Internet and am trying to run it on the tomcat server from a new Eclipse Ganymede installation. This particular project comes with its own workspace.

When I select Tomcat v6.0, I get a message

Unable to create server using selected type

Older versions of tomcat are available.

I think I need to recreate some configuration settings. The question is which one? This seems to be some kind of odd mistake, since creating a new dynamic web project allows me to configure tomcat for both of them.

Answer 1

I had a similar problem, but my solution is a bit simpler. The problem was caused by renaming the source folder referenced by the server definition.

Go to Window / Preferences / Server / Runtime, delete the broken link. Then click "Add" to create a new link, select the appropriate version of tomcat, click "Next", and you will see the wrong link to the path. Fix it. Move on.

Answer 2

I had the same issue on Ubuntu 8.10 with Ganymede and Tomcat6. This seems like a bug in Eclipse. If you try to create a server, and these are barfs, you cannot create another tomcat6 server. To resolve this issue, follow these steps:

• close eclipse
• Change to the {workspace-directory} / directory. metadata / .plugins / org.eclipse.core.runtime / .settings and delete the file org.eclipse.wst.server.core.prefs.
• run eclipse
• add your tomcat6 server in server tab

kotfu

Answer 3

@id thanks for the solution, but something is also hidden in org.eclipse.jst.server.tomcat.core.prefs

So, to solve the problem

• close eclipse
• go to {workspace-directory} /. metadata / .plugins / org.eclipse.core.runtime / .settings
• delete org.eclipse.wst.server.core.prefs and org.eclipse.jst.server.tomcat.core.prefs files

Tomcat 5.5

I want to use the tomcat5.5 server to have a catalytic catalytic file that can be written as indicated in

• http://dev.eclipse.org/newslists/news.eclipse.webtools/msg16795.html (= add READ and WRITE permissions to the files in the {$ tomcat.home} / conf directory (chmod -vR a + rw { $ tomcat.home} / conf / *) To be more specific, in the file “catalina.policy.” After that, the Tomcat server can be added on Eclipse servers)
• (dead link) http://webui.sourcelabs.com/eclipse/issues/239179 and so that tomcat5.5 stops before entering the eclipse and starts later.

Tomcat 6

To be able to use the tomcat6 server, the correct solution is to have a custom tomcat6 server instance as described in

• /usr/share/doc/tomcat6-common/RUNNING.txt.gz
• RUNNING.txt (on WEB)

My configuration is Debian / Sid, Eclipse 3.4.1. Ganymede

Answer 4

Error mapping is really the key. There are many details - if necessary, right-click on the entries and copy their contents into your favorite text editor. One of the problems that may arise, for example, is that if you have already configured the server configuration and one of the XML configuration files cannot be parsed, the server cannot be added. This happened to me tonight - my <Context> element had a string in it, so it was <C (linebreak) ontext> . This prevented Eclipse from reconstructing the server configuration.

Answer 5

In the end, I managed to work with the default Ubuntu 8.10 tomcat. (command line debugging on eclipse is a wonderful thing). First I had to make a couple of symbolic links, and then change the file permissions. (you may need to think twice about changing permissions depending on your configuration, but if eclipse cannot read the file that it throws and the exception and gui will not let you continue)

 sudo ln -s /etc/tomcat6 /usr/share/tomcat6/conf sudo ln -s /etc/tomcat6/policy.d/03catalina.policy /usr/share/tomcat6/conf/catalina.policy sudo chmod a+r /usr/share/tomcat6/conf/tomcat-users.xml 

Answer 6

Hum this can be tricky. Bring the server view. If your project has already been deployed, remove it from the server to clear the binding between your project and the server.

Or you can right-click on the project in the project explorer and select debug on the server. If you have not already done so, Eclipse will ask you to create a working server environment, and here you can specify Tomcat 6 and indicate the installation location of your server.

You can also see a “problem” view to see any problm in the imported project, such as JDK, etc.

Answer 7

Look at the error window. If you tried to install once once and failed, Eclipse seems to try to look there again later, before allowing you to create a new one. If you deleted the folder or it is not there, you need to replace it to continue.

Answer 8

The only way I found using Tomcat 6 is to change the ownership of the Tomcat directory for my user. It seems that having r / w permissions is not enough.

BTW, removing org.eclipse.wst.server.core.prefs erases your workspace configuration.

Answer 9

I had the same problem until I went to the tomcat6 configuration directory and added user rights to my user in addition to root:

cd / usr / share / tomcat6 / conf

chown root: myusername./*

chmod 777./*

You can choose the best chmod for security, 777 is just a quick brutal fix. I have Eclipse 3.5 (Galileo) + Fedora 12 + Tomcat 6 extracted from tar (which is why Eclipse was unable to access it). Eclipse complained: "Unable to create a server using the selected type."

Answer 10

What version of Eclipse? Europa? Ganymede?

What do you mean by workspace? The Eclipse workspace is not what you deploy, it contains your projects.

You will need to create a WAR file (or a folder with files that will contain the WAR file), the project usually includes ANT or Maven build script, or if the project uses Eclipse The type of dynamic web project may have the option “generate WAR " Without further details I can no longer help.

Answer 11

Adding a new dynamic web project to the workspace seems to “unlock” this feature.

Answer 12

I was changed by a change in ownership of my user.

Answer 13

In my case, these were corrupted Tomcat configuration files. Eclipse magazine said:

 org.eclipse.core.runtime.CoreException: Could not load the Tomcat server configuration at C:\Program Files\Apache Software Foundation\apache-tomcat-6.0.14\conf. The configuration may be corrupt or incomplete. 

Got a new Tomcat distribution, deleted the old one and everything is fine now.

Answer 14

Finally, this problem is resolved in my system.

1) got rid of seconded cats

2) installed a typical tomcat from bunkers on tomcat.apache.org

3) got rid of my openjdk

4) installed sun jdk (apt-get)

5) deleted my web projects in eclipse

6) noticed that when adding a web project you can install "Target Runtime" - I tried to configure it on Tomcat 6 and he informed me that there was a problem

Perhaps none of this mattered, but here is what could have mattered:

7) KICKER: Window → Settings → Server - runtime. Here all harsh runtimes have been removed and the path to my newly installed tomcat has been added.

Answer 15

This question is probably old. But I ran into this problem. My project was not recognized as a web project (without the globe logo in Eclipse).

Suppose you use the maven plugin, it could not convert to a web project with the command

 mvn eclipse:eclipse -Dwtpversion=1.5 

In the Package Explorer, right-click the project project / configure / Convert to Java Facets / Dynamic Web Project in Eclipse Et Voilà

Check the .project file in the root before and after the conversion. You will see a new nature.

 <natures> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature> <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.eclipse.wst.common.project.facet.core.nature</nature> <nature>org.eclipse.wst.jsdt.core.jsNature</nature> </natures> 

Answer 16

Instead of deleting configuration settings files, go to "Settings" → "Server" - "Runtime Environments" and delete the "forgotten" environment.

Answer 17

Thanks for this answer working for me.

I had a similar problem, but my solution is a bit simpler. The problem was caused by renaming the source folder referenced by the server definition.

Go to Window / Preferences / Server / Runtime, delete the broken link. Then click "Add" to create a new link, select the appropriate version of tomcat, click "Next", and you will see the wrong link to the path. Fix it. Move on.