Excessive Resource Adapter JCA connection creation and latency during IdleRemover execution in JBoss EAP

Solution Unverified - Updated -

Issue

  • When using a JCA resource adapter, the number of active/idle connections increases significantly (e.g., tens of thousands) even if max-pool-size is set to a low value (e.g., 100). This leads to severe response time delays (over 1 minute) when the IdleRemover thread triggers, as it blocks the pool while processing a massive volume of connection destructions.

  • Resource adapter connection pool usage increasing by min-pool-size on each connection request and the max-pool-size does not seem to be applied in JBoss EAP

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.x
  • Resource Adapter with <security><application/></security> configuration

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