Connection leak detection enforced at the end of NOT_SUPPORTED remote EJB calls in JBoss EAP

Solution Verified - Updated -

Issue

  • During execution of an EJB method invoked via the remote interface, a connection is obtained and not released
  • When the cached connection manager (CCM) debug facility is enabled to troubleshoot connection leaks, it reports a leak at the end of the remote interface method execution and force-closes the leaked connection.
  • This behavior is different from previous releases.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.1 and later
  • IronJacamar (JCA) 1.4 and later

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