SQLWarning instances on prepared statements consume significant memory in JBoss EAP
Issue
Hibernate does not clear SQLWarning instances from statement handles. As a result, significant memory may accumulate on each connection.
Environment
-
Red Hat JBoss Enterprise Application Platform (EAP)
- 5
- 6
-
Hibernate
- Hibernate 3
- Hibernate 4
-
Database
- All
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.