Managed beans not being destroyed upon log out for Liferay Portal hosted on Jboss

[anand206]

Hi Experts,

We have a Liferay Primefaces JSF Web Application hosted on a Jboss Server. During performance testing, we observed the heap memory going higher and after some thousands of operations the server getting stalled. When we examined the Heap Dumps the we observed that not all the managed Beans created are being destroyed up on log out. So these beans are getting piled up after thousands of operations contributing to the memory issues.

Below screenshots show the objects loaded before/after log out,

Before Logout:

Post Logout:

When we check for the references for these beans all of them are locked due to reference in ConcurrentreferenceHashMap which is in turn held by WebInjectionProvider.

I did a lot of googling about the same and tried below suggested solutions but none worked for me,

1. 1) Update Mojarra (JSF API, JSF IMPL) jars
2. 2) Update Jboss Web Jar
3. 3) Disable Tag pooling and Injection

Please help suggest any possible solutions for this issue.

Thanks in advance.

[ctomc]

And version of the server is?

[anand206]

Hi Tomaz Cerar,

Sorry I missed this. Jboss server version is 7.1.1. Liferay version is 6.2

[theplaystation]

update your jboss-as-web-7.1.1.Final.jar from this link

https://docs.google.com/file/d/0B60QpJIz1_HeclVuR3pZTjBzRDA/edit

i edited class WebInjectionContainer field instanceMap from

ConcurrentReferenceHashMap.ReferenceType.STRONG -> WEAK like WildFly does and it 's working for me.

http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-web/7.1.1.Final/org/jboss/as/web/deployment/WebInj…

[sahoora]

Hi

I am facing the same issue with Jboss-portal-6.1.1 and it's using jboss-as-web-7.2.1.Final-redhat-10.jar.

We have multiple portal environment and all sessions are getiing invalidated on portal logout; however all the managed beans are holding reference to WebInjectionContainer.

[anand206]

theplaystation : Thank you very much. The solution has worked for me.

@Rabindra Sahoo, You can change the jboss-as-web-7.1.1 jar as per the advice, replace the same with existing one and give it a try.