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-519) Concurrency issues due to ServletPortletInvoker being used as singleton
Date Fri, 07 Apr 2006 16:56:23 GMT
     [ http://issues.apache.org/jira/browse/JS2-519?page=all ]

David Sean Taylor reassigned JS2-519:
-------------------------------------

    Assign To: David Sean Taylor

> Concurrency issues due to ServletPortletInvoker being used as singleton
> -----------------------------------------------------------------------
>
>          Key: JS2-519
>          URL: http://issues.apache.org/jira/browse/JS2-519
>      Project: Jetspeed 2
>         Type: Bug

>   Components: Container
>     Versions: 2.0-FINAL
>  Environment: Solaris 8, Oracle 9, Java 1.5
>     Reporter: Ethan Adams
>     Assignee: David Sean Taylor
>     Priority: Critical

>
> Was running load tests and found several exceptions that seemed to say that a portlet
was being rendered in the wrong fragment window.
> After looking around, I found that the ServletPortletInvoker is configured to NOT be
a singleton, but because it is referenced in the constructor of the PortletInvoker singleton
it (ServletPortletInvoker) is being used as a singleton.
> Confirmed this behaviour by adding log entry in the constructor and found it was only
instantiated once even though several portlets were rendered.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message