Connection leak detection enforced at the end of NOT_SUPPORTED remote EJB calls in JBoss EAP
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 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.
