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

[THREDDS #WNQ-683971]: automatic dataset update without Tomcat restart



Hi Massimiliano,

I'm afraid the updating of expired catalogs does not reinitialize any of the 
dynamic dataset configuration. Which means that any changes or additions to 
datasetRoot, datasetScan, datasetFmrc/featureCollection, or any NcML datasets 
will not be updated with the reloading of an expired catalog.

It is on our list to rework the reinitialization of TDS configuration and allow 
for more dynamic changes to the configuration. We don't have a timeline for 
that yet. I'm guessing it won't happen till TDS 4.4.

Ethan

Massimiliano Drudi wrote:
> Dear Support,
> i got a problem using the expires attribute into the catalog element.
> Actually i do not know if what i am trying to do is correct.
> 
> We run a daily update of the catalog, and the expires attribute is
> always setted on the following day.
> 
> 
> Our first solution, was to restart tomcat after the catalog update is
> complete.
> 
> Then, looking to logs/catalogInit.log , i find out that TDS try to
> reread expired catalogs. Indeed in our new solution, we do not restart
> TDS, because it manage to reread the catalog by itself. This operation
> seems correct, in the catalogInit.log appears:
> ---------1
> Rereading expired catalog
> [/home/vmdap/apache-tomcat-5.5.23/content/thredds/MYOv01-MFS-FC.xml].
> [2010-11-05T08:31:26GMT]
> readCatalog(): full
> path=/home/vmdap/apache-tomcat-5.5.23/content/thredds/MYOv01-MFS-FC.xml;
> path=MYOv01-MFS-FC.xml
> readCatalog(): valid catalog -- ----Catalog Validation version 1.0.01
> ---------1
> 
> and opening the catalog via web browser, it is updated.
> 
> 
> But something is still wrong, because if i try to open a new dataset
> (one of the dataset added after the last update), i will get this
> message on the browser:
> ---------1
> Error {
> code = 404;
> message = "myov01-med-ingv-ssh-forecast20101104";
> };
> ---------1
> 
> 
> 
> Moreover, if i try to open a modified dataset, i will get this message
> on the browser:
> ---------1
> Error {
> code = 404;
> message =
> "/mnt/nfs1/vmdap/myo_v1/v1-med-ingv-forecast/20101103/20101103_dm-INGV--ASLV-MFSs4b-MED-b20101103_fc-fv01.00.nc
>  (No such file or
> directory)";
> };
> ---------1
> The message is correct, because that file doesn't exist any more, but
> after the catalog update, that file is no more used by the dataset
> (=TDS is using the dataset as it was before the update).
> 
> 
> 
> 
> If i restart Tomcat, everything goes fine, but would be nice run the
> catalog update without execute the restart of Tomcat. Is it possible?
> In our current configuration i experienced that TDS reread the
> catalog, but new/modified dataset/s don't work correctly.
> 
> 
> Regards,
> Massimiliano Drudi
> 
> 
> PS the catalog is: http://gnoodap.bo.ingv.it:8080/thredds/MYOv01-MFS-FC.html


Ticket Details
===================
Ticket ID: WNQ-683971
Department: Support THREDDS
Priority: Urgent
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.