Robin Schimpf created WFLY-12671: ------------------------------------ Summary: Memory Leak of PersistenceUnitMetadataImpl Key: WFLY-12671 URL: https://issues.jboss.org/browse/WFLY-12671 Project: WildFly Issue Type: Bug Affects Versions: 17.0.1.Final Reporter: Robin Schimpf Assignee: Brian Stansberry Attachments: Trying_to_catch_memory_leak_with_more_trace_logging.patch, memory leak after 4 deployments.PNG, memory leak after 5 deployments.PNG, persistence-unit-not-stopped.txt, persistence-unit-stopped.txt After updating from Wildfly 13 to Wildfly 17 we noticed a slowdown of our application after multiple deployments to the application server without restarting it between the deployments. Heapdumps are showing that after redeployment the number of {{PersistenceUnitMetadataImpl}} are growing (see screenshots). We are deploying 2 ear files and 2 war files. Only one ear has a database connection configured. We are using the bundeled hibernate version of Wildfly 17. The ear structure is like the following: {noformat} - app.ear | |- META-INF | |- lib | | | |- all dependencies | |- own jars and wars (e.g. jpa) {noformat} Since I failed to create a reproducing project for this behaviour I added some trace logging (Patch attached). The only difference I noticed was that sometimes the {{Stopping Persistence Unit}} logstatement is missing before the {{Stopped subdeployment}} logstatement. -- This message was sent by Atlassian Jira (v7.13.8#713008)