Database Connection Pool connection selection strategy (FIFO/MRU vs FILO/LRU) in JBoss EAP
Issue
- EAP 6 is keeping more database connections alive than EAP 5
IdleRemover
is not removing as many connections in EAP 6 as EAP 5
- EAP 6.1.0 is keeping more database connections alive than EAP 6.0.x
- Database connections are not closed (timed out), even if the load is less and not all connections are needed
- Connections are not closed even if the CLI command
/statistics=pool:read-attribute(name=InUseCount)
shows that there is a minimal load
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
- 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.