It's not a secret anymore!
The moose likes IDEs, Version Control and other tools and the fly likes Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem" Watch "Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem" New topic

Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem

Sebastian Green
Ranch Hand

Joined: Jan 30, 2004
Posts: 136
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:

Application Server Directory: C:\Programme\Apache Software Foundation\Tomcat 5.0
Port: 8080
Classpath Variable Name: TOMCAT_HOME
Classpath Variable: C:\Programme\Apache Software Foundation\Tomcat 5.0

Server Classpath

JDK_TOOLS (set to c:\j2sdk1.4.2_03\lib\tools.jar)

Client Classpath

nothing yet configured

Project Classpath


Starting Tomcat out of the Lomboz View fails with the following Stacktrace:

Bootstrap: Class loader creation threw exception
at org.apache.catalina.loader.StandardClassLoader.<clinit>(
at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(
at org.apache.catalina.startup.Bootstrap.createClassLoader(
at org.apache.catalina.startup.Bootstrap.initClassLoaders(
at org.apache.catalina.startup.Bootstrap.init(
at org.apache.catalina.startup.Bootstrap.main(
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(
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
at org.apache.commons.logging.LogFactory.getLog(
at org.apache.tomcat.util.compat.JdkCompat.<clinit>(
... 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(
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
... 10 more
Caused by: java.lang.NullPointerException
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(
... 11 more

Is the Classpath incomplete?

Thank you for your help in advance.


/ Sebastian<br />No blog, No homepage, No life?
Robin Verduijn

Joined: Jul 31, 2004
Posts: 2
Hi Sebastian,

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.
Robin Verduijn

Joined: Jul 31, 2004
Posts: 2
Also, what might help is to make sure your directory setup is in the standard Tomcat 5.0 structure, i.e:
|\_ 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.

Good luck,
Jo Seib

Joined: Aug 07, 2004
Posts: 1
found helpfull hints at
i.e. change endorsed dir paramter to just .../common/endorsed
I agree. Here's the link:
subject: Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem
It's not a secret anymore!