There seems to be a scalability problem in the PortletSetFactory:
For each user, a PortletSetFactory object is created that holds a Portlets
tree
representing the user's PSML file. I guess the tree can become quite big in
terms
of memory usage.
The PortletSetFactory object is stored in the SingletonHolder and
apparently
is never removed. If the number of users is large, the memory of the server
may
be used up after running for some time.
Is there a particular reason for not putting the PortletSetFactory object
into the
HttpSession ?
This would allow the JVM to garbage-collect the PortletSetFactory and the
referenced
Portlets tree after the HTTP session expires.
Best regards,
Thomas
Thomas Schaeck
IBM Pervasive Computing Division
Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED]
Address: IBM Deutschland Entwicklung GmbH,
Schoenaicher Str. 220, 71032 Boeblingen, Germany
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
