-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.0.5 GA
-
Fix Version/s: --Sprint - SP, 6.1.0 CE RC1
-
Component/s: ~[Archived] WCM
-
Labels:None
-
Branch Version/s:6.0.x, 5.2.x
-
Backported to Branch:Committed
In render_portlet.jsp you will find the following code :
if (portlet.isActive() && access && supportsMimeType) {
try {
invokerPortlet.render(renderRequestImpl, renderResponseImpl);
....
} catch (UnavailableException ue) {
portletException = true;
PortletInstanceFactoryUtil.destroy(portlet);
}
It will actually destroy the portlet when an UnavailableException is thrown while per spec, it should only do this when the UnavailableException is permanent
Here is the relevant excerpt from jsr286
PLT.5.4.7 Exceptions During Request Handling
If a permanent unavailability is indicated by the UnavailableException, the portlet container must remove the portlet from service immediately, call the portlet's destroy method, and release the portlet object.xxiv A portlet that throws a permanent
15 UnavailableException must be considered unavailable until the portlet application containing the portlet is restarted.
When temporary unavailability is indicated by the UnavailableException, then the portlet container may choose not to route any requests to the portlet during the time period of the temporary unavailability
- relates
-
LPE-4238 Portlet 2.0 (JSR 286) Compliance - Exceptions During Request Handling
-
- Closed
-