Detect connection leaks when using non-JTA or non-CCM datasources in EAP 6

Solution Verified - Updated -

Issue

  • Datasources have been created with the jta property set to false because some applications are incompatible with JTA
    • Direct transaction control using Connection methods setAutoCommit(boolean), commit() and rollback() is incompatible with JTA
  • The Cached Connection Manager (CCM) Debug facility does not detect Connection leaks for non-JTA datasources

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.