Originally posted by Ashok Jag: Tim, I changed the port number differently say 8585 still gettting the same error.
*Which* port number did you change?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
It's not Eclipse that's the problem. Unless you start Tomcat with remote debuggin enabled, no debugging port will be opened. If you're starting from a shell script/batch file, you will probably have to actually change the startup script (some versions of this script have a comment line that tells you how to do this).
On a local machine using a J2EE development system such as the sysdeo Tomcat plugin, the plugin starts Tomcat as an embedded server and switches on remote debugging automatically, but if you're launching Tomcat yourself, you also have to switch on the debugging port yourself.
You have to tell Eclipse what port to talk to as a client - which you did. But Tomcat has to also be told to switch that port on as a debugging server.
Like I said earlier, the debugging server isn't directly related to Tomcat's being a web server - any Java application can run a debug server. It's a completely independent function.
Sometimes the only way things ever got fixed is because people became uncomfortable.