Community
Participate
Working Groups
Build Identifier: Version: 3.6.1 Build id: M20100909-0800 Install a fresh copy of eclipse v3.6.1. Show the "servers" view, right click, select New->Server. From the list of adapters, select "Apache Tomcat v6.0". When Apache Tomcat v6.0 is selected, the "finish" and "next" buttons are greyed out with no explanation, hint or clue as to what the user did wrong. It is impossible to continue, therefore no support exists for tomcat v6.0 in eclipse v3.6.1. Reproducible: Always Steps to Reproduce: xxx
Created attachment 182579 [details] Screenshot of the New->Server dialog box, showing options greyed out. Screenshot of the New->Server dialog box, showing options greyed out.
Attempting to compare this with the behaviour of v3.5. When an attempt is made to select "New->Server" on eclipse v3.5, and "Apache v6.0" is selected, this time the message "Cannot create a server using the selected type" appears at the top of the dialog box, and the finish button is greyed out. At no point did the developer who wrote this message stop and think for a second to tell the end user _why_ a server of the selected type cannot be created. If I was guessing, I would say that it might be because in this instance of v3.5, an Apache v2.0.26 server already exists, however this doesn't make any sense either - why would the end user be limited to just one server in the server view?
Do the buttons become enabled once you enter a name for the server, i.e. is this a problem of the page not indicating the field is required?
You can select the "server name" field, but you cannot type anything into it, all keystrokes are ignored, again without any explanation. I suspect what broke was the explanatory text that appears at the top of the dialog box. In v3.5, it says "cannot create a server of the requested type" (but doesn't explain why it cannot, or what the user must do to fix it, or even if what the user is expecting it to do is possible).
It must be something relate to the MacOS as I would think that a lot of people would had complaint about this. Do you see anything in the .log of the workspace? What version of JRE are you using?
The "Cannot create a server using the selected type" appears to be a generic message for "something bad happened but I don't know what". Unfortunately a bug in NewManualServerComposite.loadServerImpl() causes that message to get displayed if anything goes wrong with server creation, replacing any message that might have been useful. However, it appears that the messages that would get replaced should appear in the log file. Are there log entries from "wst.server" and "jst.server" plug-ins in the Error Log for Eclipse 3.5.x/WTP 3.1.x or Eclipse 3.6.x/WTP 3.2.x? As part of initialization of the wizard, a "working copy" for the selected or default server type is created. I assume something is causing this to throw an exception that prevents the dialog from advancing. That "something" might involve the creation of a "dummy" Server Runtime Environment for the server, when there are none already defined for that type. To verify this, does this dialog behave normally if you already have a Tomcat 6.0 Server Runtime Environment defined? Creating a "real" runtime might be able to avoid some issue that is tripping up creation of the "dummy" one. So far, I don't see anything obvious that would explain why you don't see the "Cannot create a server..." message in Eclipse 3.6 but still can't advance. I'm assuming the cause is the same for both.
I am having a similar problem. However, I was initially able to create a server. I ended up deleting the server. When I went back to re-create it, I was unable to enter anything in the server name field. I'm not using MacOS though, I'm using Ubuntu 10.10 32 bit. Build ID: 20100917-0705 Prior to this problem, I installed the Subclipse plugin on a fresh install of the build.
I've confirmed that this behavior can occur if there is a Target Runtime for that version of Tomcat which is invalid. For example, if you create a new or copy and existing Tomcat 6.0 installation and create a new Tomcat runtime and server from that copy, then delete the copy, you will get this behavior when trying to create another Tomcat 6.0 server. The problem is that WTP is trying to create a server "working copy" using the existing but bad runtime, which throws exceptions. In both WTP 3.2.x and WTP 3.2.x, you should see errors in the Error log that reveal the problem loading the configuration for the runtime that would confirm this is the cause of the behavior. I don't know why the "generic" problem message is no longer displayed in WTP 3.2.x. For now, I'm assuming this is the source of the behavior and am bumping the Importance down to "normal". Having a runtime go bad shouldn't happen that often. There is better error handling when there are problems creating Tomcat runtimes so hopefully bad runtimes aren't created accidentally. Deleting or fixing the bad runtime should avoid the behavior in this bug.
Ok I have exactly the same bug (ubuntu 10.10 & Eclipse Helios 3.6.1), but I figured out something that could go wrong on unix based system: By default, if Tomcat installation was performed by an administrator, it is possible that the permissions inside the conf/ directory are something like: -rw------- Therefore, Eclipse can't manage to read it and meets an error. To find out, I suggest you to take a look at the Error Log (Window, Show View, Other..., General, Error Log). You will see here all the errors Eclipse didn't manage to display. In my case there are a lot of "Could not load the Tomcat server configuration at /path/to/installation/of/tomcat/conf. The configuration may be corrupt or incomplete." So I went to the installation directory and made the files readable using: sudo chmod +r *.xml sudo chmod +r *.p* That did the job and fixed the problem
I had the same issue when I installed the new indigo release of Eclipse, and wanted to add the Tomcat 7 server. It would let me select any of the previous Tomcat versions, but not 7 - same issues (greyed out, no server name box, can't click next). After hours of trying things and looking for answers, comment 8 & 9 helped me figure it out... I had installed a new Tomcat and a new Eclipse, but when the workbench opened, I selected my same old existing workspace directory that I have always used. After having no luck trying to delete individual config or preference files, I completely emptied out my workspace folder so that a had a blank slate to start up with, I deleted the "new" Eclipse installation, and RE-Unzipped a whole new copy of eclipse. It started up just like BRAND NEW, I selected my freshly empty workspace directory, and TA-DA........... I was able to create a new server with Tomcat 7. (aparently, I had a preference file somewhere that was looking at my old configurations.)
I had the same problems as comment 10 with Indigo and Tomcat7 but I did not want to give up my workspace and create a new one. After deleting the two files below, I was able to create a server again. These paths are relative to the directory of your workspace: ./.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jst.server.tomcat.core.prefs ./.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.wst.server.core.prefs
Confirming the bug on Fedora 18
And the workaround works good.
The problem still seems to be present on Fedora 19/Eclipse Kepler
Are there any plans to fix this annoying bug? I am experiencing it from more than a year.
Hello, This problem is still present in Eclipse Luna for Tomcat 7.0 Server. The solution is : close eclipse go to {workspace-directory}/.metadata/.plugins/org.eclipse.core.runtime/.settings remove the files org.eclipse.wst.server.core.prefs and org.eclipse.jst.server.tomcat.core.prefs Like it's said in the forum : https://www.eclipse.org/forums/index.php/t/453143/
Is this bug still out of there???
(In reply to Germano Massullo from comment #17) > Is this bug still out of there??? I can confirm that this bug is still out there. I am running MacOS/Luna, and the behavior "seems" to be the result of deleting a server. Larry Isaacs' comment 8 "resembles" my local scenario. I had created a Tomcat 6 server, configured it to "Use the Tomcat installation (take control of the Tomcat installation)", then, subsequently deleted it. Errors occurred, and I subsequently could not add a new Tomcat 6 installation from that point forward. I hope this helps find the issue. The workaround helped greatly. Thanks.
I ran into that same problem. Comment 11 has the solution, thanks a lot ! Also, you don't actually need to remove the files. Just editing the path to tomcat in these files is enough. From what I get, you could probably do that from the eclipse user interface in Preferences>Server>Runtime Environments but I haven't tried it myself.
