Configure legacy (non-JPA) Hibernate for integration with managed JTA datasources in JBoss EAP 7

Solution Verified - Updated -


  • Using application managed Hibernate rather than the container managed JPA integration
    • Migrating a legacy (non-JPA) application to JBoss EAP
    • Using Spring managed/initialized Hibernate legacy (no-JPA) configuration
  • Configure Hibernate to use JBoss EAP managed JTA datasource pools


  • Red Hat JBoss Enterprise Application Platform (EAP) 7
  • Hibernate 5

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