[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #INI-524419]: Hello... Error with thredds?



Hi Gavin,

Gavin Bell wrote:
> Pardon, I don't know if you are the right person to send this to, but
> perhaps you can look at this trace?

The best way to get TDS questions answered is to email address@hidden That goes 
into our support system and gets answered by whoever is available rather than 
depending on me being around. Another option is the THREDDS email list 
(address@hidden). I pushed your email into our support system.

> I am using 4.2 that I built from the posted source (by the way is there
> a repository available to pull from?).

On the TDS home page there is a link in the TDS 4.2 section called "Building 
TDS from Source Code" that lists our public Subversion repository and describes 
the Ant build process we use to build the thredds.war file:

http://www.unidata.ucar.edu/projects/THREDDS/tech/TDS.html
http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/SourceCodeBuild.html

> (I'll have to get back to you on the node customization thing we
> discussed before, I have not tried it yet... have to surmount this issue)
> 
> Here it is both catalina.out and catalina.err (respectively).

The errors starting and stopping TdsConfigContextListener look like they might 
be caused by your thredds.war file not containing all the configuration 
documents needed. Similarly for the log4j error in catalina.out. The thread 
shutdown problem looks like a problem we need to look into.

How are you building your war file/directory? Take a look at the build process 
described on the source code build page (URL above) and see if that helps. 
Basically, in the tds directory, run 'ant clean makeWar'.

Ethan
 
> Oct 1, 2010 2:48:44 PM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path: /usr/local/curl/lib:/usr/local/pgsql/lib:/usr/
> local/cdat/Externals/lib:/usr/local/globus/lib:/usr/local/curl/lib:/usr/local/pgsql/lib:/usr/local/cdat/Externals/lib:/usr/local/globus/lib:/usr/local/curl/lib:/usr/local/pgsql/lib:/usr/local/cda
> t/Externals/lib:/usr/local/globus/lib:/usr/local/curl/lib:/usr/local/pgsql/lib:/usr/local/cdat/Externals/lib:/usr/local/globus/lib:/usr/local/curl/lib:/usr/local/pgsql/lib:/usr/local/cdat/Externa
> ls/lib:/usr/local/globus/lib::/usr/local/java/jre/lib/i386/client:/usr/local/java/jre/lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
> Oct 1, 2010 2:48:45 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-80
> Oct 1, 2010 2:48:46 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> Oct 1, 2010 2:48:46 PM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 2562 ms
> Oct 1, 2010 2:48:46 PM org.apache.catalina.realm.JAASRealm setContainer
> INFO: Set JAAS app name Catalina
> Oct 1, 2010 2:48:46 PM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Oct 1, 2010 2:48:46 PM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.29
> Oct 1, 2010 2:48:47 PM org.apache.catalina.startup.HostConfig deployDescriptor
> INFO: Deploying configuration descriptor thredds.xml
> Oct 1, 2010 2:48:50 PM org.apache.catalina.core.ApplicationContext log
> INFO: Initializing Spring root WebApplicationContext
> Oct 1, 2010 2:48:52 PM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance
> of class thredds.server.config.TdsConfigContextListener
> java.lang.IllegalArgumentException: Root directory must exist: 
> /usr/local/tomcat/content/thredds/public.
> at 
> thredds.util.filesource.BasicDescendantFileSource.<init>(BasicDescendantFileSource.java:59)
> at thredds.server.config.TdsContext.init(TdsContext.java:299)
> at 
> thredds.server.config.TdsConfigContextListener.contextInitialized(TdsConfigContextListener.java:64)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4135)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630)
> ...


> Oct 1, 2010 2:48:52 PM org.apache.catalina.core.StandardContext start
> SEVERE: Error listenerStart
> Oct 1, 2010 2:48:52 PM org.apache.catalina.core.StandardContext start
> SEVERE: Context [/thredds] startup failed due to previous errors
> Oct 1, 2010 2:48:52 PM org.apache.catalina.core.StandardContext listenerStop
> SEVERE: Exception sending context destroyed event to listener instance
> of class thredds.server.config.TdsConfigContextListener
> java.lang.IllegalStateException: setInstance() must be called first.
> at thredds.servlet.DataRootHandler.getInstance(DataRootHandler.java:110)
> at 
> thredds.server.config.TdsConfigContextListener.contextDestroyed(TdsConfigContextListener.java:93)
> at 
> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4174)
> at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4778)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4675)


> Oct 1, 2010 2:48:52 PM org.apache.catalina.core.ApplicationContext log
> INFO: Closing Spring root WebApplicationContext
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/thredds] appears to have started a thread
> named [TdsScheduler_Worker-1] but has failed to stop it. This is very
> likely to create a memory leak.
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/thredds] appears to have started a thread
> named [TdsScheduler_Worker-2] but has failed to stop it. This is very
> likely to create a memory leak.
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/thredds] appears to have started a thread
> named [TdsScheduler_Worker-3] but has failed to stop it. This is very
> likely to create a memory leak.
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/thredds] appears to have started a thread
> named [Timer-0] but has failed to stop it. This is very likely to create
> a memory leak.
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/thredds] appears to have started a thread
> named [TdsScheduler_QuartzSchedulerThread] but has failed to stop it.
> This is very likely to create a memory leak.
> Oct 1, 2010 2:48:52 PM org.apache.catalina.loader.WebappClassLoader
> clearThreadLocalMap
> SEVERE: The web application [/thredds] created a ThreadLocal with key of
> type [org.apache.log4j.helpers.ThreadLocalMap] (value
> address@hidden) and a value of typ
> e [java.util.Hashtable] (value [{startTime=1285969732251, ID=1}]) but
> failed to remove it when the web application was stopped. This is very
> likely to create a memory leak.

> ::::::::::::::
> catalina.out
> ::::::::::::::
> log4j:WARN No appenders could be found for logger
> (org.springframework.util.ClassUtils).
> log4j:WARN Please initialize the log4j system properly.
> TdsConfigContextListener.contextInitialized(): start.
> Exception in thread "Timer-0" java.lang.NoClassDefFoundError:
> org/apache/log4j/spi/NOPLoggerRepository
> at org.apache.log4j.LogManager.getLoggerRepository(LogManager.java:175)
> at org.apache.log4j.LogManager.getLogger(LogManager.java:199)
> at org.apache.log4j.Logger.getLogger(Logger.java:105)
> at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283)
> at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:171)
> at org.quartz.utils.UpdateChecker.checkForUpdate(UpdateChecker.java:51)
> at org.quartz.utils.UpdateChecker.run(UpdateChecker.java:39)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> 
> --
> Gavin M. Bell
> Lawrence Livermore National Labs
> --


Ticket Details
===================
Ticket ID: INI-524419
Department: Support THREDDS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.