Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Eclipse 3.0, Lomboz 3.0 & Tomcat 5.0.x problem

 
Sebastian Green
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:

"Hello,

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
Address: 127.0.0.1
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)
${classPathVariableName}/bin/bootstrap.jar

Client Classpath

nothing yet configured

Project Classpath

JDK_TOOLS
${classPathVariableName}/bin/bootstrap.jar
${classPathVariableName}/common/lib/servlet-api.jar
${classPathVariableName}/common/lib/jsp-api.jar

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

Is the Classpath incomplete?

Thank you for your help in advance.

Tobias"
 
Robin Verduijn
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

Good luck,
Robin.
 
Jo Seib
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
found helpfull hints at
http://forge.objectweb.org/forum/forum.php?thread_id=1028&forum_id=360
i.e. change endorsed dir paramter to just .../common/endorsed
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic