CLONE - The portlets cannot be displayed after a portal reload -------------------------------------------------------------- Key: GTNPORTAL-3299 URL: https://issues.jboss.org/browse/GTNPORTAL-3299 Project: GateIn Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: PC integration Affects Versions: 3.5.7.Final Reporter: Tran Trung Thanh Assignee: Peter Palaga Original Estimate: 1 day Remaining Estimate: 1 day If you launch Gatein in developing mode, it is possible to reload only a given portal container either automatically by redeploying a webapp that has been defined as a PortalContainerConfigOwner (in other words you have the listener org.exoplatform.container.web.PortalContainerConfigOwner in your web.xml) or manually using the JMX console. And when you do so, no portlet can be displayed properly anymore (we have the message "This portlet encountered an error and could not be displayed" for all portlets), this issue is due to https://issues.jboss.org/browse/GTNPORTAL-2406. Here are the steps to reproduce: * Start GateIn with ./standalone.sh -Dexo.product.developing=true * launch the JMX Console and call _reload_ with the argument _portal_ on the MBean {{exo:container=root}} * Once the command is over, go to http://localhost:8080/portal/