Memory Leak In WebLogic 11g When Restarting With JPA Application Deployed In It
(Doc ID 1596793.1)
Last updated on JUNE 07, 2022
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
When having an application deployed in WebLogic 10.3.6 and restarted, that application becomes stuck in heap memory after undeploying it (its classloader is not available for garbage collection).
It only seems to happen when the application uses JPA with a custom implementation declared in META-INF/persistence.xml file. And only happens if the application is already deployed and the application server is restarted. Hibernate 3.4.0.GA is being used as JPA implementation inside an EJB jar.
If the application is deployed and undeployed without a server restart then it works fine.
The memory leak happens in both WebLogic (10.3.6.0) and (10.3.0.0). The difference is, in WebLogic10.3.0 the web console shows an exception stack trace when trying to undeploy the application. In WebLogic 10.3.6, a success message is shown indicating no server restart is necessary, although a restart is still necessary.
The main concern is with version 10.3.6 as customer is migrating all the server from version 10g to 11g.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document