Using the CachedConnectionManager to identify leaked connections

Solution Unverified - Updated -

Issue

  • Do you suggest to change the settings to true for "track unclosed connections and close them"?
  • Attempting to identify unclosed connections

Environment

  • Red Hat JBoss Data Services 5.3.1
  • Red Hat JBoss Enterprise Application Platform (EAP) 5
  • The CachedConnectionManager bean defined in jca-jboss-beans.xml
  • debug defined by the CachedConnectionManager
  • Client application suspected of not properly closing connections.

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