Although I've seen quite a few errors posted concerning Tomcat Startup errors...I haven't found this one.
First of all, Tomcat starts up fine when I don't use the Sysdeo Plugin with Eclipse. When I do use it, I get an error on startup. The odd thing is that it doesn't even give me a stack trace in the console and doesn't write ANYTHING to the logs. I do receive this stack trace in the debug window of Eclipse, however:
org.apache.catalina.startup.Bootstrap at localhost:2679 Thread [main] (Suspended (exception FileNotFoundException)) URLClassPath$JarLoader.getJarFile(URL) line: not available URLClassPath$JarLoader.<init>(URL, URLStreamHandler, HashMap) line: not available URLClassPath$3.run() line: not available AccessController.doPrivileged(PrivilegedExceptionAction<T> line: not available [native method] URLClassPath.getLoader(URL) line: not available URLClassPath.getLoader(int) line: not available URLClassPath.getResource(String, boolean) line: not available URLClassLoader$1.run() line: not available AccessController.doPrivileged(PrivilegedExceptionAction<T>, AccessControlContext) line: not available [native method] Launcher$AppClassLoader(URLClassLoader).findClass(String) line: not available Launcher$AppClassLoader(ClassLoader).loadClass(String, boolean) line: not available Launcher$AppClassLoader.loadClass(String, boolean) line: not available Launcher$AppClassLoader(ClassLoader).loadClass(String) line: not available Launcher$AppClassLoader(ClassLoader).loadClassInternal(String) line: not available Bootstrap.<clinit>() line: 53
At which point the thread is suspended and I have to manually kill it in Eclipse to stop it. The eclipse debugger also typically brings up the file and the line associated with the error in the stacktrace, or tells you if you do not have that particular sourcecode loaded for that piece of code. The latter appears in this case with the following info:
URLClassPath$JarLoader.class Source not found The jar file rt.jar has no source attachment.
Now the even ODDER thing is that I had the plugin working just fine for about 30 minutes before the business above started to transpire. All I was doing when it happened was editing a context file for a particular application. However, in the meantime, I've completely taken that context file out (and all other ones) and it still hasn't done anything, so I think maybe that was a coincidence.
Here's some system information: Oracle 10g Drivers Windows XP Pro JDK 1.5.0_04 Eclipse 3.1 (Stable Version)
I do find it odd that my 1.5 isn't already in my path variable, but 1.4.2 from Oracle's install is. Would that have anything to do with it? I've had the Oracle 9i drivers hose things up in the past, but not like this.
I discovered that if I check the box in Eclipse under Tomcat >> JVM Settings that says "Don't run Tomcat in Debug Mode" it will run fine. Hmmm. Unfortunately, using the debug mode in Eclipse is one of the main reasons I use the plugin!
Oddly enough, I ended up resolving this error by simply switching workspaces in Eclipse. This is really only a workaround, as I still don't know what caused the problem except that it looks like it was workspace specific. If anyone has any ideas as to what the cause of this was exactly I'd truly appreciate it.
Hopefully this workaround will at least help someone else in the future!
"...and the Truth will set you free."
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop