SQLWarning instances on prepared statements consume significant memory in JBoss EAP

Solution Verified - Updated -

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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content