[hibernate-dev] report of a WildFly memory leak that may come from hibernate service loader...

Steve Ebersole steve at hibernate.org
Mon Jul 15 14:53:40 EDT 2013

My guess would be that the service registry is not being released.  Let me

Brett, that makes me wonder if we ever properly deal with releasing the
OSGi classloader stuff...
contains the details about deployment level classes are leaking (CDI
beanmanager passed into deployment, bean validation factory, others...).

In WildFly 8, We do have a

file that contains org.jboss.as.jpa.hibernate4.DefaultJtaPlatform

The org.jboss.as.jpa.hibernate4.DefaultJtaPlatform is a system module
class but could also be an application deployment class.

Question:  Do we have a way to unload services that have been loaded
when the original classloader (deployment) is no longer needed (e.g.
when SessionFactory is closed)?

I'm not sure that would help for the leak that I am reproducing which
could be a different problem.

By the way, this is with Hibernate ORM 4.3.0.Beta3.

hibernate-dev mailing list
hibernate-dev at lists.jboss.org

More information about the hibernate-dev mailing list