I discovered this subtle bug when deploying my latest
release to our (load balanced) test environment.
As part of the forum changes, I amended the way the
Recent Forum Postings portlet works so that it was a
bit more restricted. This involved PersistentPortal
invoking a method on the portlet config for each
portlet type in the database when putting together
the homepage.
Portlet Config is registered to the portlet type
during initialization. The problem I encountered was
when a new portlet type was loaded. Once loaded on
one server, the app type is listed in the database,
and so retrieved by PersistentPortal on the other
server. But until the other server is restarted, the
initializer for the new portlet hasn't run and so the
config is null, hence a big NullPointerException when
you navigate to the homepage. This small patch just
checks for that condition. After applying this, I
deployed the new portlet type to production without
any problems.
Chris....
Patch must be applied over patch 1459849