NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Examining the environments between the working and non-working tomcats, I notice that the tds.log.dir system property is not set in the non-working tomcat environment. I assume that is a side-effect of the listener failing and the context not starting. --john John Cartwright wrote: > I neglected to mention that TDS 3.x works find on this same > OS/tomcat/JVM configuration. > > --john > > > John Cartwright wrote: > >> Hello All, >> >> we're trying to run TDS 4.x on a RHEL5 server using the Redhat-supplied >> tomcat (5.5.23). Unable to get it to start, presumably because the >> listener TdsConfigContextListener is failing to start. Catalina.out shows: >> >> TdsConfigContextListener.contextInitialized(): start. >> Jun 17, 2009 3:44:11 PM org.apache.catalina.core.StandardContext start >> SEVERE: Error listenerStart >> Jun 17, 2009 3:44:11 PM org.apache.catalina.core.StandardContext start >> SEVERE: Context [/thredds] startup failed due to previous errors >> >> Everything works fine in a binary install of tomcat on the same machine >> which suggests some kind of classpath problems. Can anyone suggest what >> classes might be the problem? Any other ideas on what the problem might >> be? >> >> Thanks! >> >> --john >> >> _______________________________________________ >> thredds mailing list >> thredds@xxxxxxxxxxxxxxxx >> For list information or to unsubscribe, visit: >> http://www.unidata.ucar.edu/mailing_lists/ >> >> > > _______________________________________________ > thredds mailing list > thredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ >
thredds
archives: