| The managed connection pool (mcp) configuration is exposed in the subsystem configuration schemas. To define in standalone-full.xml you set the mcp attribute on the datasource node in the datasources subsystem. e.g (example from a EAP7.0.1.GA runtime):
<server xmlns="urn:jboss:domain:4.1"> |
... |
<subsystem xmlns="urn:jboss:domain:datasources:4.0"> |
<datasources> |
<datasource jndi-name="java:/jdbc/Example" pool-name="Example" mcp="org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool"> |
<connection-url>jdbc:mysql://...</connection-url> |
... |
</datasource> |
</datasources> |
</subsystem> |
... |
</server>
|
EAP team routinely defines the SemaphoreConcurrentLinkedDequeManagedConnectionPool managed connection pool as it is a fully supported connection pool that performs better under heavy contention than the default pool. |
