When I hit the portal with a url from an expired session. For example http://portal.../uPortal/render.userLayoutRootNode.uP?uP_root=root&uP_sparam=activeTab&activeTab=2.
Instead of displaying the guest page I get several problems. The first one is a described in
Once that NullPointerException is elliminated I get:
ERROR [http-443-5] portal.ChannelManager. Mar/13 06:47:44 - Encountered a portal exception while trying to start channel rendering! :
org.jasig.portal.PortalException: Could not find a transient node for id: u7l1n10
That's not too too surprising since the old session was dead I suppose but it doesn't clear up. Once this problem occurs it does not go away. Even if I hit the portal from another browser on another machine the error behavior continues. The screen shots showing that uportal thinks I am editing a fragment show the behavior. When I use the normal url to the portal with no parameters I see the image attached as up3expiredguestnoparms.jpg. The second is when I hit tab2 and is attached as up3expiredguesttab2.jpg.
It looks to me like I am running into issues related to the new impersonation support. It gets even more interesting if I actually get myself a CAS session - then I get two messages to exit the fragment. Image attached as up3expiredguestCASsession.jpg.
I suspect the Could not find a transient node problem has been around a long time since our logs are full of an older variant which I bet is due to CAS gateway and guest timeouts. It used to report the node as ctf1 and the new message reports more meaningful data. Our old error is completely transient and has no effect on the user experience as far as I can tell.