On Thu, Jan 20, 2005 at 10:01:18AM +1100, Kathie Manson wrote: : Up until yesterday, I was happily running tomcat 4.1.30. Then, for : some reason, I started getting this error. I'm not sure why. It's : likely that I somehow changed the class path, or installed something : else that affected some other java classes, but I just don't know how : to fix it.
At the risk of sounding flippant, try to think of what has changed recently. Can you check your backups and compare that list of JAR files (or even /classes dirs) to what's installed on the server? -and when you say you "reinstalled" Tomcat, how dod you do it? Did you remove the old version, then replace it with the new version? or did you overwrite the old with the new? In the latter case, any rogue (extra) JARs that are lying around won't be affected. Finally, are you certain that's the full stack trace? Those usually come with a "Root Cause" section that can be quite helpful. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
