Hello all, There was some discussion a few weeks ago on uportal-user about some installations' channels all seeming to not want to render. Everyone (us included) who reported problems had recently deployed the WeatherPortlet. We found out that the portlet does not set a timeout for a connection or a read in its current version. This was addressed by Dustin Schultz yesterday on portlet-dev when he posted his patches for it.
During this process, we found that we were seeing this message in our logs (we log at WARN in production): WARN [TP-Processor3] portal.ChannelRendererFactoryImpl.[] Oct/02 10:40:20 - queueSize: 1094 activeCount: 20 largestPoolSize: 20 The render requests were getting considerably backed up. Some folks on the list said they did not see this message in their logs. I have a patch I would like to contribute that would log this message as an error. We found it to be a valuable clue to help us figure out that it wasn't necessarily a problem with uPortal. A lot of folks in that thread, however, seem to log at error only. Furthermore, as more and more portlets use downstream content, this could be a good indicator as to when something is going wrong. Thoughts? -- Andy Gherna CITES, University of Illinois Senior Research Programmer Email: [EMAIL PROTECTED] Phone: (217)265-9490 -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
