Tomcat Port problem at http://localhost:8080/EclipseRootContext

[Michele Smith]

Hello, I was working on trying to make three different workspaces work concurrently with the Mongrel.jar file in the wee wee hours of the morning today. The reason why is that I am developing three different workspaces right now. I am a little unclear as to how to associate them so that they can use each other's meta data. I have done some research on the web about setting up multiple workspaces and did not find anything very useful. I have one app that I have developed that was working fine, but I had a couple of apps that were freeware that I wanted to evaluate and potentially change and possibly link to the main workspace, but I kept getting errors on those apps when I tried to use them. I did send in the errors and was directed by another individual on this forum to evaluate the net.sf.mongrel_1.0.0.jar, which I did get ahold of and put in the appropriate place in Eclipse. After I did these things I got all kinds of errors when I tried to associate any of the projects in the workspace with the Apache Tomcat Server 7.0.

I don't know what happened, but I had to take Eclipse off the machine, delete all workspaces inside the Eclipse workspace before taking Eclipse off the machine, and I also took this opportunity to download Luna, the most current release. I am using JDK 1.7 and JRE 1.6 There is a reason for this I cannot control my work environment -- it is simply bolted down.

I did a netstat and a netstat -a and did not see anything unusual there. I saw one instance of port 8080 being utilized: at 127.0.0.1:8080

No matter what I do now, I get this error after I put the Tomcat plugin into Eclipse (again, I have to install the Tomcat plugin into Eclipse Luna, because my environment is bolted down):

Several ports (8005, 8080, 8009) required by Tomcat v7.0 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).

I do see the welcome page at http://localhost:8080 -- but I am not sure how to get rid of the aforementioned error. I have never had to manually delete a port before and hesitate to do so. Right now I have that one .war file imported back into the workspace and the others are not in there. I know that the .war file would import successfully earlier and am really concerned about how to get the localhost up and running. I am really needing any suggestions anybody can provide.

If you have any ideas, please let me know.

Thanks,
Michele

[Tim Holloway]

I'm confused. When you work on a project, it's an assumption that everything that you work on is going to be in a single workspace. I don't even know how to have multiple workspaces active at the same time short of running multiple instances of Eclipse. Which would be resource-intensive and - to me, anyway - confusing. The Metadata is not supposed to be stuff that's essential to or integral with a project itself - it's supposed to control how you interact with Eclipse within the workspace instance, so sharing it sounds like a debatable thing to do.

For example. Let's say you've got 3 copies of Eclipse, with 3 different workspaces. Each copy of Eclipse is a separate JVM. Meaning that right off the bat, JVM memory is not shared between them. I seriously doubt that Eclipse workspace metadata is designed to have instances of Eclipse hitting it at once. Which means that the first clueless person who did a "switch workspace" into an already active workspace would be courting trouble.

Let's say that each one has a Tomcat project in it (doesn' matter here if it's mongrel or WTP). When Eclipse launches Tomcat, each Tomcat is going to be in a separate JVM, and each JVM is a separate process, therefore each Tomcat is going to have to be explicitly defined with a distinct and non-conflicting set of HTTP, HTTPs, control and proxy ports.

Workspace meta-data is what defines how that's done. In the case of sysdeo/mongrel, it holds the filename path to JAVA_BASE, whose lib/configs.xml file defines the ports. Obviously, then, this particular bit of workspace meta-data cannot be shared between the 3 tomcat instances/workspaces.

Then again, the whole concept of "evaluating the mongrel.jar" confuses me, too. Mongrel isn't a jar that you incorporate into a project, it's a plug-in to Eclipse. So you'd evaluate Mongrel by installing the plugin. And, if you don't like it, by later de-installing it.

Finally, assuming that you're running 3 copies of Eclipse all from the same Eclipse directory, they'll all 3 reference the same plug-in. But since they're 3 different JVMs, the actual mongrel plugin classes will load separate copies, one into each JVM. And reference the mongrel meta-data for the particular workspace that that particular instance of Eclipse has active. It gets even messier if you're trying to run completely separate editions of Eclipse at the same time (for example, Kepler and Luna or 2 Lunas with different plugin sets).