Flush strategies for datasource connection pools in JBoss EAP

Solution Verified - Updated -

Issue

  • What flush strategy should I use?
  • What are the FLUSH strategies in JBoss datasource connection pools?
  • When does JBoss flush the pool?
  • If we set the the flush strategy on the pool to EntirePool, does that interrupt or force-close active connections that are otherwise functional?
  • What are the implications of using the flush operation for datasources via the Jboss Management console?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6
    • 7
  • Use of the flush-strategy attribute as defined by the following schemas in <JBOSS HOME>/docs/schema:
    • jboss-as-datasources_1_0.xsd
    • jboss-as-datasources_1_1.xsd
    • jboss-as-datasources_1_2.xsd
    • jboss-as-resource-adapters_1_0.xsd
    • jboss-as-resource-adapters_1_1.xsd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.