This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I found this post on another forum, Im having the same problem and havent been able to solve so any kind of help would be nice.
Here is the message:
I just installed Eclipse 3.0, Lomboz 3.0 and Tomcat 5.0.27 on my Windows XP. But now I'm wondering how to configure Lomboz to successfully start Tomcat out of the Lomboz View in Eclipse? In the past I used the Sysdeo Tomcat Plugin, which does his job very well.
Under Workbench/Preferenzes/Lomboz/Server Definitions I had chosen Apache Tomcat v5.0.x and set the properties as follows:
Starting Tomcat out of the Lomboz View fails with the following Stacktrace:
Bootstrap: Class loader creation threw exception java.lang.ExceptionInInitializerError at org.apache.catalina.loader.StandardClassLoader.<clinit>(StandardClassLoader.java:207) at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:189) at org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:160) at org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:104) at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:193) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:399) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.tomcat.util.compat.JdkCompat.<clinit>(JdkCompat.java:55) ... 6 more Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException (Caused by java.lang.NullPointerException) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) ... 10 more Caused by: java.lang.NullPointerException at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:374) ... 11 more
I had exactly the same problem you describe. Eventually, I found that if I removed an older xalan.jar file from the common/endorsed directory, everything would be okay. In your situation, perhaps you could try removing each jar from your common/lib, common/endorsed and server/lib directories to find out which jar is causing the problem. Hopefully, this will work for you as well.
Joined: Jul 31, 2004
Also, what might help is to make sure your directory setup is in the standard Tomcat 5.0 structure, i.e: TOMCAT_HOME |\_ bin | |\_ common | |\_ endorsed | | | \_ lib \_ server \_ lib
The xml-apis.jar and xercesImpl.jar have to be in TOMCAT_HOME/common/endorsed. This may or may not help, but I found that changing my non-standard lib directories around helped fix the problem.