Announcement Announcement Module
Collapse
No announcement yet.
"Error reading tld listeners" - HELP! Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Error reading tld listeners" - HELP!

    Hi al!!
    Im working on a web application. Im using Tomcat 5.5.20 as web container.
    The problem is when i put some beans into my applicationContext.xml file. When Tomcat starts it throws an exception:

    Code:
    31/01/2007 09:18:22 org.apache.catalina.core.StandardContext processTlds
    SEVERE: Error reading tld listeners java.lang.NullPointerException
    java.lang.NullPointerException
    	at org.apache.log4j.Category.isEnabledFor(Category.java:746)
    	at org.apache.commons.logging.impl.Log4JLogger.isTraceEnabled(Log4JLogger.java:327)
    	at org.apache.catalina.startup.TldConfig.tldScanResourcePaths(TldConfig.java:581)
    	at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:282)
    	at org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4302)
    	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4139)
    	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
    	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
    	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
    	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
    	at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
    	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
    	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
    	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
    	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
    	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
    	at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
    	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
    	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
    	at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    	at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
    	at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
    	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:585)
    	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
    	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
    If i remove this new bean, the application works ok...
    I dont know wat to do.. i need put more bean (datasource, propertyConfigurer, etc)
    The jar libraries of Log4j and commons-logging are in the classpath of application.
    Im using Spring 2.0.1 and Spring WebFlow 1.0.1.

    Some help??!!
    Thank you!

  • #2
    Ok, Im remove from my WEB-INF/lib the log4j-1.2.14.jar and the application runs ok now...
    But, what appens if I want user log4j for logging?

    Comment


    • #3
      I came across this today while working on an application. The complexity was minimal, but i was using various common's libraries and hibernate (with it's respective default dependencies).

      I haven't dove into the code (commons logging and spring), but I strongly believe the problem lies within the initialization of the context and errors produced when the application starts. For example I can easily reproduce the problem by intentionally misconfiguring a spring bean or hibernate mapping.

      Unfortunately I had to do a lot of trial & error debugging to find the original problem in my configuration because logging was unavailable at that point.

      I strongly feel this is not an issue with the version commons logging (or log4j) as I am using the latest stable release. I didn't have to revert to an older release in order to resolve the issue either.

      If anyone is interested, I can create a war that replicates the problem consistently.

      Comment


      • #4
        Hi, I got the same error.

        In my case it was caused by a badly map type between the model object hibernate annotation tag and the a column type.

        It's defenetly not an issue with the log4j. It's more likely an error in the initialization of the context done by Spring and the error reporting.

        Hope this helps!

        Comment

        Working...
        X