Hi Prabha,
what is the load on you machine?
We implemented a special cleanup valve that cleans up the fragments
after each request. It helped to improve the memory foot print.
Joachim
/* (non-Javadoc)
* @see
org.apache.jetspeed.pipeline.valve.impl.CleanupValveImpl#invoke(org.apache.jetspeed.request.RequestContext,
org.apache.jetspeed.pipeline.valve.ValveContext)
*/
public void invoke(RequestContext request, ValveContext context) throws
PipelineException {
super.invoke(request, context);
ContentPage page = request.getPage();
if (page != null) {
Fragment root = page.getRootFragment();
cleanFragmentsTree(root);
}
}
/**
* Disconnect content fragment from fragment definition.
*
* @param root parent fragment
*/
private void cleanFragmentsTree(Fragment root) {
if (root != null) {
List fragments = root.getFragments();
if (fragments != null && fragments.size() > 0) {
//Process child fragments
Iterator it = fragments.iterator();
while (it.hasNext()) {
Fragment child = (Fragment)it.next();
cleanFragmentsTree(child);
}
}
//Clean the given fragment
if (root instanceof ContentFragment) {
((ContentFragment)root).setPortletContent(null);
}
}
}
Am 20.08.2010 03:31, schrieb prabha77:
>
> Hi all,
>
> We are currently using Jetspeed 2.1.3 with pages stored in oracle.
> Sometime back we had issues with database page manager.
> We backported some of the code from JETSPEED-2.1.3-POSTRELEASE related to
> Distributed Database Page Manager EhCache Cache Backport - backport
> Now Once in every two days, the portal is resulting in OutOfMemoryError.
>
> Looking at the heap dumps it looks like almost of the 50% of memory is
> alloted to PageImpl and FragmentImpl. Dominator Tree in eclipse MAT shows
> PageImpl and FragmentImpl when Grouped by Class as the top most objects in
> the memory.
> Solving this issue is really important for us to move the application to
> Production.
>
> I really appreciate any help in solving the issue.
>
> Thanks
> Prabha
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
