You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2008/03/24 03:11:25 UTC
[jira] Updated: (JS2-800) Memeory Leak Caused by
org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl
[ https://issues.apache.org/jira/browse/JS2-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated JS2-800:
--------------------------
Fix Version/s: 2.2
Adding this feature to 2.2 too now.
I will commit the synchronization of this feature to trunk shortly
> Memeory Leak Caused by org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl
> ------------------------------------------------------------------------------------------
>
> Key: JS2-800
> URL: https://issues.apache.org/jira/browse/JS2-800
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1.2
> Reporter: Scott T Weaver
> Assignee: Scott T Weaver
> Fix For: 2.1.3, 2.2
>
> Attachments: PortletWindowAccessor.Png, TopObjects.Png
>
>
> org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl uses a straight HashMap to cache instances of portlet windows. In high-usages environments this can cause enough of a memory leak to crash the JVM.
--
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