Hi Roland:
Sorry I forgot about this. Heres a bit more info.
The idea is that we can want to cache the NetcdfFile objects in memory.
Previously, our ability to cache was limited by the IOSP holding on to
finite system resources like file handles. So typical use case is for the
IOSP to close its file on release() and to reopen it on acquire(). Probably
safe for you to implement as NOOPs.
/**
* Release any system resources like file handles.
* Optional, implement only if you are able to reacquire.
* Used when object is made inactive in cache.
* @throws IOException
*/
void release() throws IOException;
/**
* Reacquire any resources like file handles
* Used when reactivating in cache.
* @throws IOException
*/
void reacquire() throws IOException;
On Thu, Jul 30, 2015 at 9:10 AM, Roland Schweitzer - NOAA Affiliate <
roland.schweitzer@xxxxxxxx> wrote:
> I have an IOSP that I plug in to TDS. It has served us well for many
> years. With the latest TDS our ISOP fails half the time because TDS calls
> the new reacquire method for which we have no implementation.
>
> Error {
> code = 500;
> message = "gov.noaa.pmel.tmap.iosp.FerretIOServiceProvider.reacquire()V";
> };
>
>
> I have no clue what the methods is supposed to do or how to implement it.
>
> Can somebody please add some information the Java doc about this method to
> explain how this should be implemented?
>
>
> http://www.unidata.ucar.edu/software/thredds/current/netcdf-java/javadocAll/index.html
>
> Thanks,
> Roland
>
> _______________________________________________
> thredds mailing list
> thredds@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
