portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Assigned: (JS2-646) ActionValveImpl can throw NullPointerException under clustered environment.
Date Thu, 25 Jan 2007 17:53:49 GMT

     [ https://issues.apache.org/jira/browse/JS2-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Sean Taylor reassigned JS2-646:

    Assignee: David Sean Taylor

> ActionValveImpl can throw NullPointerException under clustered environment.
> ---------------------------------------------------------------------------
>                 Key: JS2-646
>                 URL: https://issues.apache.org/jira/browse/JS2-646
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Components Core
>    Affects Versions: 2.1
>         Environment: Servlet Container: Tmax JEUS 5.0 (Fix #17).
> The #17 fixes were reported to Tmax by our portal dev team and included the followings:
>   - JAAS bug fixes.
>   - Fixes for Spring portlet MVC framework Loading problems.
>   - Fixes for Webtob's 'URI too long' problem.
> I'm going to post installation guide document for that platform later. (I have to translate
>            Reporter: Woonsan Ko
>         Assigned To: David Sean Taylor
>         Attachments: JS2-646-diff.txt
> When servlet containers are clustered, ActionValveImpl can throw NullPointerException
as follows:
> ActionValveImpl.java:initWindow.window.getPortletEntity()[null]
> java.lang.NullPointerException
>         at org.apache.jetspeed.pipeline.valve.impl.ActionValveImpl.initWindow(ActionValveImpl.java:187)
>         at org.apache.jetspeed.pipeline.valve.impl.ActionValveImpl.invoke(ActionValveImpl.java:88)
>         at org.apache.jetspeed.pipeline.JetspeedPipeline$Invocation.invokeNext(JetspeedPipeline.java:166)
>         at org.apache.jetspeed.container.ContainerValve.invoke(ContainerValve.java:77)
>         ...
> The reason why this symptom occurs is that the cache for portlet windows is shared among
containers, but the portlet entity for a portlet window cannot be synchronized among containers.
> So, a portlet window can be retrieved from the cache, but its portlet entity can be null.
> Therefore, I added a path to check if portlet entity is null, and to refresh the portlet
window with validated portlet entity. See my patch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message