Hi, I would just like to confirm what I understand about how the rss news feeds work, in particular when a news feed becomes unavailable. If I have configured jetspeed with an rss portlet that is external to my webserver and the server hosting the rss file goes down, based on what I've seen in the JetspeedURLManagerService and what I've read in the documentation, the next time the diskcache mechanism checks for an update to the news feed and is unable to reach it, the status for that url in the urls Hashmap (and written out to services.URLManager.url as defined in JetspeedResources.properties) is set to URLManager.STATUS_BAD (14 in my case).
Is this correct so far? Is this what is referred to in http://jakarta.apache.org/jetspeed/site/diskcache.html in the last sentence: "Bad URL monitoring: Jetspeed keeps track of URLs that it can't fetch. If it is ever restarted it will reload this so that time isn't wasted on failed content. "? Later the server hosting the rss file comes back up and I want jetspeed to keep checking like it does for updates to the news feed. It seems that once the url is marked as bad there are no further attempts to reach it. We have had to stop tomcat and delete the datasources.properties file and restart tomcat to get it to again access the rss url. I have the following questions I appreciate your help with: 1. Is it true that urls are 'black listed' in this way in the datasources.properties file (or the file named in the services.URLManager.url property)? 2. Is it true that once a url is marked as bad, no further attempt is made to access it until it is removed from the list (by deleting the properties file) and then requested via a request for the portlet? 3. Is there some way to configure jetspeed so that it tries to access 'bad' urls to see if they are once again accessible? Thanks in advance for any wisdom anyone can share. Lori -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
