Hi Patrick,
That's really strange behavior. I'm curious, what happens if you (temporarily) rename the index directory? Does the system still function? In which case, it must be holding onto open files which shouldn't ever happen.
For the record there should be no results caching within XTF.
Does restarting the servlet container (e.g. Tomcat) resolve it? That would be another clue, though clearly it wouldn't be a good long-term solution to be constaintly restarting the container.
--Martin
--You received this message because you are subscribed to the Google Groups "XTF Developer list" group.
To post to this group, send email to xtf-...@googlegroups.com.
To unsubscribe from this group, send email to xtf-devel+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xtf-devel?hl=en.
Martin (et al),
I've gotten together with my sysadmin to do a little further testing with this issue. First, I did remove the index directory (I temporarily moved it up a few levels outside of the xtf hierarchy of the filesystem). This did not seem to have any noticeable impact on the xtf application (site still could be browsed without any trouble). I attempted restarting the servlet container, but the old data was still present (even after a reindex). I tried using an incremental rather than clean reindex, this didn't make a difference in the shown-in-webpage (vs. on the filesystem) content (it still had old data). What my sysadmin and I did notice is that it seemed as though the application (tomcat or xtf, I didn't really understand which) was "holding on to open files" (these were my sysadmin's words). Specifically, they were "*.cfs" file paths which no longer existed on the file system but were present in memory. I'm guessing that this has something to do with the issue.
We are running Tomcat 6.0.26 as our servlet container, but could upgrade to 6.0.29 (though it's probably not likely that this will make a difference). I tried to confirm what version of XTF we are running, but alas the CHANGES.txt, INSTALL.txt, and README.txt all link out to the xtf website rather than containing specific release information.
I'm not sure what else to try at this point. Any tips, hints, resources, or recommendations would be appreciated.
- Patrick E.
PS - Some sample content of the open but non-existent files:
We are running Tomcat 6.0.26 with the latest version being 6.0.29, so an upgrade to Tomcat is available.
patrick 24702 0.0 -0.2 29684 4940 p1- S 16Nov10 0:31.49 /usr/bin/perl -w ./xtf_proc.pl <http://xtf_proc.pl/>
Hi Patrick,
It just gets more mysterious, eh? I don't think the Tomcat version will make any difference at all. I'm starting to wonder if there might be two XTF directories involved instead of just one. For instance, if you make a minor (but visible) change to your display stylesheets, does that change show up in the web interface? If not, that's a really sure sign that you're not touching the right directory.
Also, check your textIndexer.conf file (under tomcat/webapps/xtf/conf) and make sure that its <src> path is correct.
I seriously doubt that the Tomcat version has any bearing.
--Martin
Martin (et al),
I've gotten together with my sysadmin to do a little further testing with this issue. First, I did remove the index directory (I temporarily moved it up a few levels outside of the xtf hierarchy of the filesystem). This did not seem to have any noticeable impact on the xtf application (site still could be browsed without any trouble). I attempted restarting the servlet container, but the old data was still present (even after a reindex). I tried using an incremental rather than clean reindex, this didn't make a difference in the shown-in-webpage (vs. on the filesystem) content (it still had old data). What my sysadmin and I did notice is that it seemed as though the application (tomcat or xtf, I didn't really understand which) was "holding on to open files" (these were my sysadmin's words). Specifically, they were "*.cfs" file paths which no longer existed on the file system but were present in memory. I'm guessing that this has something to do with the issue.
We are running Tomcat 6.0.26 as our servlet container, but could upgrade to 6.0.29 (though it's probably not likely that this will make a difference). I tried to confirm what version of XTF we are running, but alas the CHANGES.txt, INSTALL.txt, and README.txt all link out to the xtf website rather than containing specific release information.
I'm not sure what else to try at this point. Any tips, hints, resources, or recommendations would be appreciated.
- Patrick E.
PS - Some sample content of the open but non-existent files:
We are running Tomcat 6.0.26 with the latest version being 6.0.29, so an upgrade to Tomcat is available.
patrick 24702 0.0 -0.2 29684 4940 p1- S 16Nov10 0:31.49 /usr/bin/perl -w ./xtf_proc.pl <http://xtf_proc.pl/>