Heavy memory footprint on brix AdminPanel

[jhteo]

We used brix cms on our prototype application. 

We're very happy with all the feature provided by brix and the way of wicket development.

But, there's a serious problem we're facing now.

We have 15 content authors doing content concurrently using Brix provided content admin panel to author

content. The application is running out of memory within 15 mins due to out of memory error.

The application is using default settings running on 2GB Heap with 32 bit IBM Websphere 7.

Can anybody give any advise on how this is issue can be resolved?

- JH

[Igor Vaynberg]

Can you profile it and see where the memory leak is?

-igor

> --
> You received this message because you are subscribed to the Google Groups "brix-cms-discuss" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/brix-cms-discuss/-/1MMBsaEUrxUJ.
> To post to this group, send email to brix-cms...@googlegroups.com.
> To unsubscribe from this group, send email to brix-cms-discu...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/brix-cms-discuss?hl=en.
>

[jhteo]

The caused has been identified, its not a problem on the AdminPanel. 

Actually it is caused by using org.springframework.web.context.support.SpringBeanAutowiringSupport at component

instantiation listener.

After taking it away. It seems to run fine.

But there's another problem on memory spike when using the MenuPlugin.

According to observation by JProfiler, the call stack on 

brix.plugin.menu.Menu.load() resulted in over 100 stack size being called, which

caused a lot of memory used (100 concurrent view == 1.7G used) and lot of gc happening. 

Too bad we had to put the Menu plugin a side. :(

[jhteo]

The problem comes up again.

The error happens on displaying pages with markup exception.

How to reproduce:

1. Create a page with rather big html content.

2. Make a form tag with mismatch tag.

3. Preview the page, the page will shows MarkupException being thrown.

4. Keep on clicking the preview.

Eventually server will crash due to OutOfMemoryError (failed to create stack trace)