Disabling or deleting a datasource does not disconnect all connections in EAP 6.2
Issue
-
If you are using the max connections of your datasource and you abruptly delete or disable that datasource, a race condition occurs during connection destruction in which a ‘RetryableException’ recreates the pool with the min number of connections.
-
When you disable or delete your datasource, you see the following DEBUG log with a
RetryableExceptionwhile the pool connections are being destroyed. You need TRACE logging enabled.09:06:40,041 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http-/127.0.0.1:80-1) Got a RetryableException - trying to reinitialize the pool 09:06:40,042 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (http-/127.0.0.1:80-1) Register pool: SemaphoreArrayListManagedConnectionPool@546f8396[pool=testpool] (interval=300000)
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 6.2
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.
