Tomcat Integration - LogConfigurationException

Hello,
Just trying to setup a webapp project with Tomcat integration and am running into an annoying exception. I get the following exception when IDEA attempts to startup tomcat:

org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:558)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:355)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at org.apache.commons.digester.Digester.]]>(Digester.java:345)
at org.apache.catalina.startup.Catalina.createStartDigester(Catalina.java:280)
at org.apache.catalina.startup.Catalina.start(Catalina.java:441)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Caused by: java.lang.NullPointerException
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:543)
... 12 more
Process terminated with exit code 0

Any suggestions?
Thanks,
Ryan Cuprak

14 comments

What is the version of Tomcat you are using?

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Ryan Cuprak" <jiveadmin@intellij.net> wrote in message news:5787875.1046882783353.JavaMail.jrun@is.intellij.net...

Hello,
Just trying to setup a webapp project with Tomcat integration and am running into an annoying exception. I get the following

exception when IDEA attempts to startup tomcat:
>

org.apache.commons.logging.LogConfigurationException: java.lang.NullPointerException
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:558)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:355)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:409)
at org.apache.commons.digester.Digester.<init>(Digester.java:345)
at org.apache.catalina.startup.Catalina.createStartDigester(Catalina.java:280)
at org.apache.catalina.startup.Catalina.start(Catalina.java:441)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Caused by: java.lang.NullPointerException
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:543)
... 12 more
Process terminated with exit code 0

>

Any suggestions?
Thanks,
Ryan Cuprak



0

I'm having the same error show up when trying to integrate Tomcat with my webapp. I'm using Tomcat v4.1.18 with IDEA v3.0.1 Any help would be much appreciated, and if you need more info, let me know!

-a

0

I'm also able to generate the same exception when starting Tomcat from inside IDEA (Build 696). I'm using version 4.0.6 of Tomcat. The exception is not generated if I start Tomcat externally.

Grant

0

So if I understood right, you are not using Tomcat plugin, but invoke Tomcat by creating a Run configuration? In this case the
reason could be that you haven't configured properly all startup parameters (see Tomcat's startup scripts for how they should be
configured ).

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Grant Lewis" <jiveadmin@intellij.net> wrote in message news:3769123.1047592961362.JavaMail.jrun@is.intellij.net...

I'm also able to generate the same exception when starting Tomcat from inside IDEA (Build 696). I'm using version 4.0.6 of Tomcat.

The exception is not generated if I start Tomcat externally.
>

Grant



0

Eugene, I think that the problem is that now the Tomcat plugin can properly work just with the 4.0.5 version (as the IDEA says).
As you can see, Grant Lewis uses 4.0.6 version and he got the problem.
I got the same problem with the Tomcat 5.0, though I could debug applications when I had Tomcat 4.0.4 installed.

Lizard

0

For me it works fine with version 4.0.6.

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Roman Boroday" <r.boroday@softhome.net> wrote in message news:20113346.1048200785989.JavaMail.jrun@is.intellij.net...

Eugene, I think that the problem is that now the Tomcat plugin can properly work just with the 4.0.5 version (as the IDEA says).
As you can see, Grant Lewis uses 4.0.6 version and he got the problem.
I got the same problem with the Tomcat 5.0, though I could debug applications when I had Tomcat 4.0.4 installed.

>

Lizard



0

The problem is that there's something awry with the new tomcat's and JDK 1.4.1.x

Starting tomcat 4.1.18 and 4.1.24 through the plugin using JDK1.3.1, and everything's sweet. Change the project's JDK to use 1.4.1, and it'll crap out with a "LogConfigurationException". Swap back down to 1.3.1, and everything's sweet again.

If I had to shoot from the hip, I'd say that something really tiny is being missed in the tomcat plugin. Can start it through Ant just fine mimicing tomcat's bootloader configuration.

One thing I notice though...
In the newer tomcat's (4.1.x), there's an extra endorsed directory (or at the very least, a lib directory), and the tomcat plugin only seems to be using "$CATALINA_HOME/common/lib", where as there is now also...
"$CATALINA_HOME/common/endorsed"... which happens to contain the xerces implementation, which would be why commons-digester is keeling over.

But, I tried moving the startup string to a batch file where I added the extra endorsed directory, but it didn't work either.

Who knows. But the work around for now is to use the latest tomcat, JDK1.3.1 for running in IDEA, but do final testing by running tomcat from it's own batch file or ANT using 1.4.1.x

Annoying, but workable...

0

The main purpose of the plugin is to provide JSP source-level debugging which does not work with Tomcat 4.1.x. Thus the plugin
supports only 4.0.x versions of Tomcat.

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"



0

I have no beef with the fact that the plugin is meant to run with the debugger, but the stance is to simply ignore the minor advantages of working with the plugin?...

Like being able to browse from exceptions, not having to switch from the IDE to a console, as well as being able to get to the output using Idea's key mappings?... all because it can't run the debugger with it?...

0

I would formulate it in another way: the plugin allows both running and debugging of Tomcat. Additional benefit is that when Tomcat
is started with the help of the plugin, you get source-level JSP debugging. The known limitation (that is also mentioned in the
documentation) is that plugin requires Tomcat 4.0.x versions and is not guaranteed to work with other Tomcat versions. The plugin
also serves as a reference implementation of the open API allowing to extend debugger's possibilities to debug JSP pages. That's why
sources for the plugin are provided and you are free to modify them.

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Arron Bates" <jiveadmin@intellij.net> wrote in message news:1335640.1049006900118.JavaMail.jrun@is.intellij.net...

I have no beef with the fact that the plugin is meant to run with the debugger, but the stance is to simply ignore the minor

advantages of working with the plugin?...
>

Like being able to browse from exceptions, not having to switch from the IDE to a console, as well as being able to get to the

output using Idea's key mappings?... all because it can't run the debugger with it?...


0

Well, reverting to the 1.3 JDK is not an acceptable answer for me. Can someone tell me if the non-eap version of idea's debugger works with the tomcat plugin and jdk 1.4? If not, this is a big problem. I'm trying to convince people I know to choose idea over other ide's like eclipse, but if I can't even get the debugger to work, then I've already lost that debate. I might as well start using eclipse too. Please someone tell me there is a way to make this work!

0

The debugger of IDEA 3.0.x works fine with JDK 1.4 and Tomcat 4.0.x
What problems do you have?

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Matt Ruhn" <matt.ruhn@dch.com> wrote in message news:6304462.1051045970727.JavaMail.jrun@is.intellij.net...

Well, reverting to the 1.3 JDK is not an acceptable answer for me. Can someone tell me if the non-eap version of idea's debugger

works with the tomcat plugin and jdk 1.4? If not, this is a big problem. I'm trying to convince people I know to choose idea over
other ide's like eclipse, but if I can't even get the debugger to work, then I've already lost that debate. I might as well start
using eclipse too. Please someone tell me there is a way to make this work!


0

I'm getting the same Exception described at the start of the thread. I'm running Tomcat 4.1.24-LE with JDK 1.4.1_02. Due to some other problems with our app, I can't go back to an earlier version of tomcat either. So will it work with these? If so, do you know how? Thanks!

0

As I have already mentioned many times before, the plugin won't work with Tomcat 4.1.x because they dropped the feature allowing the
plugin to calculate positions in JSP code while debugging.
If plugin's functionality does not suit you, you are free to modify plugin's sources - they are included in the distribution.

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Matt Ruhn" <mruhn@yahoo.com> wrote in message news:448118.1051108700715.JavaMail.jrun@is.intellij.net...

I'm getting the same Exception described at the start of the thread. I'm running Tomcat 4.1.24-LE with JDK 1.4.1_02. Due to some

other problems with our app, I can't go back to an earlier version of tomcat either. So will it work with these? If so, do you know
how? Thanks!


0

Please sign in to leave a comment.