You’d think this would be a bad file error, but it wasn’t. Turned out the portalDataSource connection pool had gone bad, preventing the desktop from being found or loaded. Again, you’d think that a restart of the server would fix that, but it didn’t. I had to un-deploy and re-deploy the connection pool before things started working again.
This was on WebLogic Portal 10.3.2. I haven’t seen it before, but that doesn’t necessarily mean it is restricted to that version.
Using the Content Presenter Portlet to add content will be unreliable if server affinity is not configured for the cluster. The portlet will reset itself mid-task. This may not be the case if session replication is turned on, though, as I ran across this in the early stage of the project. Still, something useful to be aware of.
I ran across a thread on LinkedIn that pointed me to an excellent article on IT on Guard dealing with a slow WLS start up issue.
This thread is a must-read if you are a consultant or ever thought of being one. Free LinkedIn membership required.