This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
John, Our bad. Because of some port confusion (we have 8 tomcat w/ proxies), we were "reloading" the wrong tomcat. So "reload" works fine, as expected. ("reinit" still doesn't work, but you knew that). Thanks, Rich On Wed, Nov 24, 2010 at 12:57 PM, Richard Signell <address@hidden> wrote: > John, > Is this documented in the TDS 4.2 pages? > Even it it is, perhaps it's worth posting to the TDS group to avoid > folks getting confused (as I did). > > Most people I know who run a TDS use reinit or reload after making > catalog changes. > > -Rich > > On Wed, Nov 24, 2010 at 12:34 PM, John Caron <address@hidden> wrote: >> On 11/24/2010 8:12 AM, Rich Signell wrote: >>> >>> John, >>> Another user of our devel 4.2 server showed me that neither "reinit" from >>> debug or "reload" from the tomcat admin GUI reflected the changes she made >>> to the catalog XML. I confirmed this. Any ideas what could be wrong with >>> out installation? >>> >>> -Rich >> >> 1) dont use reinit for now, ill try to get it working in 4.3 again >> 2) from tomcat manager, you should do an "undeploy", then "deploy" and point >> to the thredds.war file. or just restart tomcat. "reload" will not work. >> > > > > -- > Rich Signell > 81 Queen St > Falmouth, MA > -- Rich Signell 81 Queen St Falmouth, MA