[gcstang]

Operating System and version : XP Pro
Eclipse version and build id : 3.0 and 200310101454
MyEclipse version : 3.6.4
JDK version : 1.4.2_02
Steps to reproduce the problem.

Deployed a WAR project to Tomcat 5.0.3 as an expanded WAR and Start Tomcat in debug mode. Works fine then if you stop it using the Tomcat5 Stop it shuts down however if you try to then start it you get an error about URL:

URL.setURLStreamHandlerFactory(URLStreamHandlerFactory)line: 980 [local variables unavailable]

The only way to clear this is by restarting Eclipse.

Is there a way to fix this?

[support-michael]

Try this:

0) stop all Java processes (verify using TaskManager)
1) restart Eclipse
2) check count of JVMs running; there should be 1 (use TaskManager)
3) launch Tomcat from MyEclipse connector and verify that 2 JVMs are running
4) stop Tomcat using MyEclipse connector and check JVM process count. It should be 1. How many JVM process are running at this time?

Michael
MyEclipse Support

[gcstang]

I did as you said and there were two after starting tomcat and then one after shutting tomcat down. However after trying to restart it again still receive the error.

Also when trying to stop this new start up I get an error:

Catalina.stop : java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
…

The only way to stop it is either through taskmanager or stop button in the debug window, however unless you restart Eclipse it gives you the same error every time.

[Scott Anderson]

Catalina.stop : java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect

This is typically the error you get when you’ve requested a stop and tomcat isn’t running.

Have you customized your Tomcat installation in any way, such as by modifying the xml configuration files? Are you making changes to the Tomcat classpath on launch? If you only stop exclusively with the Eclipse debugger’s stop button, instead of requesting a graceful stop using the MyEclipse connector, does the problem still persist?

–Scott
MyEclipse Support

[gcstang]

Stopping with the Debugger causes the same problem. I have nothing defined in the classpath; I did have the lib directory for Tomcat and the tools.jar in it but tried it without as well and the same problem is encountered.

I also did not change any settings in the server.xml the only thing that was added is a context.xml in the location
<install dir>\conf\Catalina\localhost\context.xml

This only defines a DB Pool.

Thank you,

[Scott Anderson]

This could also be an issue with the 5.0.3beta version of Tomcat. You might try upgrading to the latest beta to see if the problem persists.

–Scott
MyEclipse Support

[gcstang]

You were correct I upgraded to tomcat 5.0.14 and myeclipseide is working as it did in a prior version.

Thank you for your assistance.

[Author]

Posts