Detect connection leaks when using non-JTA or non-CCM datasources in EAP 6
Issue
- Datasources have been created with the
jtaproperty set tofalsebecause some applications are incompatible with JTA- Direct transaction control using Connection methods
setAutoCommit(boolean),commit()androllback()is incompatible with JTA
- Direct transaction control using Connection methods
- 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.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
