• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Eclipse and invalid ports

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Having heard all the "hubbub" concerning Eclipse, I decided it was time to abandon my trusty text editor and dive into all that is Eclipse. All was going well, classes compiling etc. until I went to run the webapp. I recieved the following message:

"The server cannot be started because one or more of the ports are invalid. Open the server editor and correct the invalid ports."

By the way, Tomcat is running fine on port 8080.

Any ideas?

I'm using Eclipse 3.2 w/WPT, Tomcat 5.5.12, JRE 1.4.2_11 and the necessary compatibility jars.

Could the problem have something to do with the compatability jars? I'm really not sure what the issue is here.

Thanks.
 
Saloon Keeper
Posts: 27752
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Eclipse doesn't use any tcp/ip ports. Most likely you did something that attempted to start a second copy of Tomcat. For example, if you tried to launch the sysdeo Tomcat debugging system while running a standalone Tomcat.

In a case like that, you would either forgo sysdeo and connect as an external debugging client to the standalone tomcat, shut down the standalone tomcat and use only the sysdeo tomcat session, or - if your standalone tomcat is running stuff unrelated to your debugging, change the config (server.xml) for the sysdeo Tomcat to not use any of the ports that the standalone Tomcat uses, so that the two Tomcats don't get in a fight.

I speak specifically for sysdeo's plugin, because I know and use it, but other plugins can be expected to act in a similar way.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic