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.
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.
John Caron wrote: > Hi John: > > We dont use JNDI but default Tomcat probably does, so it may be a > problem. I just checked around and no one at Unidata has used > RHEL-supplied tomcat. But I think Greg Keith just went through this, > so his advice may be pertinent. > > It would be good if you kept this email going publically on the > thredds list if you're willing, so others can learn/contribute. > > John Thanks John. Sounds like Greg has his working now but was dealing w/ different problems than I seem to have. I don't think the "missing" JNDI jar file is affecting tomcat since it runs fine w/o the thredds.war in place. It's got to be something about the RHEL-packaging of tomcat or permissions but I don't see it. $CATALINA_HOME/content/thredds is owned by tomcat and has rwx permissions. Examining the tomcat environment confirms that it's using the RHEL-supplied Sun 1.6.0_14-b08 JVM. Does it make sense to you that tds.log.dir system property would fail to be set if a context listener fails and therefore the context fails to start? --john
thredds archives: