The problem is that the portlet configuration is stored in the session when lazy loading a portlet. The PortletRenderer stores the config when rendering the dashboard and then when the request makes it out to the LazyLoadingPortletServlet, it retrieves the config and then removes it from the session. This will NPE if you make two requests at the same time. The first request gets the info and removes the session object. The second request can then not find the object in the session and it dies.

One way around this is to pass enough information in the request such that we can just lookup the portlet config from the db. There is no good way of doing this at the moment other than going to the db. Will need the portlet config id and some better mechanism than just grabbing the GV to make this happen.