2 Replies Latest reply on Jul 1, 2015 6:43 PM by davidfdr.davidfdr.gmail.com

Stateful Session Bean and memory leak in EAP61 or JBOSS 711

davidfdr.davidfdr.gmail.com Apr 10, 2015 2:13 PM

I have encountered a system using severals rest services (Resteasy) making lookup on SFSB and theses beans are in memory holding hibernate session and persistence context causing a memory leak (they never die).

We have notice that each call to SFSB generetes a new instance (Using BeanProvider.getContextualReference(BeanThatKillMemory.class) and this instance never gets destroyed or passivated. (The current cache config is "simple" on standalone.xml).

These beans do not have a timeout configured.

I do not find in any place of the code a call to a method anotated with @Remove annotation. So, it is obrigatory call a method with @Remove or properly configure a EjbTimeout correct?

1. Re: Stateful Session Bean and memory leak in EAP61 or JBOSS 711

croco Apr 10, 2015 4:59 PM (in response to davidfdr.davidfdr.gmail.com)

If you want to use the same instance of the SFSB je have to hold the reference to the bean. This is not a proxy like for SLSB where you get every time an instance from the pool, you are given an actual instance. But why don't you use SLSB so you won't have this kind of problems if you have requests from web service?

When you want to close your conversation with the SFSB you have to call the method annotated @Remove.

You were asking about timeouts, Take a look at this: https://developer.jboss.org/wiki/HowDoTheTimeoutsWorkWithEJB3StatefulBeans
1 of 1 people found this helpful
Actions
2. Re: Stateful Session Bean and memory leak in EAP61 or JBOSS 711

davidfdr.davidfdr.gmail.com Jul 1, 2015 6:43 PM (in response to croco)

Thank you by your answer. We manage to change all stfb to stateless and and called the @Remove annotated methods.

Now the system is OK.
Actions

Go to original post