Channel Rendering Problem

0
No votes yet

We've been having a problem with the built in channels - particularly (considering their importance) the campus and personal announcements. These last are high in importance to many of our staff users who see a useful granularity here that isn't really available so readily elsewhere. Sungard seem to have worked out the problem - that it's some kind of incompatibility between portlets and channels - and perhaps relates to the underlying uPortal implementation. Anyway, we've been doing various things to mitigate the problem and since the problem is, at least, identified, we're hoping there will be a fix soon. Since it's a Java problem - to do with JSPs, Tomcat and uPortal - it would seem likely that anyone else on IV.x might well have seen the same problem - but you would have to be using JSP portlets (i.e. portlets that use JSPs for the view). I would have thought that this would mean most portlets, but.... Anyway, we need both portlets (of which we've now a small but useful group) and the built in channels. If you have had the same problem, let us know. We're on windows, but this would seem to be a cross platform bug. Of course, perhaps GNU/Linux will prove to be OK...

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Channel Rendering Problem

Maybe I am missing something, but what error message are you receiving? If the channel itself fails to render, you should get able to view a stacktrace either in the window, or in the $CP_ROOT/logs/cp.log file.

stacktrace, etc

Hello

We certainly do get stacktraces - they usually start something like:

Inner exception:
org.jasig.portal.PortalException: A problem occurred rendering JSP '/WEB-INF/uPortal\com/sct/pipeline/uportal/channels/logo/logo.jsp'. Response Error Code: 404, Response Error Message '/WEB-INF/uPortal/com/sct/pipeline/uportal/channels/logo/logo.jsp' at org.jasig.portal.channels.jsp.Channel.renderCharacters(Channel.java:235) at....

and so forth. It's believed that the 404 is something to do with confusion of some sort in the rendering queue - the queue of pages to render - and it looks like portlets and channels don't seem to queue properly if you've got both on a luminis tab.

Luminis have very helpfully got a fix to us and we are now trying it out. If you've experienced this problem, please let us know.

best wishes

Steve

Further info

A patch, 4.0.2.25, was produced for this, and so far this seems to be working fine.