Connection Lazy Enlistment in EAP

Environment

• Red Hat JBoss Enterprise Application Platform (EAP) 5, 6
• EAP 5 configuration in server.xml in the directory JBOSS_HOME/jboss-as/server/<PROFILE>/deploy/jbossweb.sar
• EAP 6 configuration in <standalone|domain>.xml in JBOSS_HOME/<standalone|domain>/configuration
  • jboss-as-datasources_1_0.xsd
  • boss-as-datasources_1_1.xsd
  • jboss-as-datasources_1_2.xsd

Issue

• What is connection lazy enlistment?

Resolution

Lazy enlistment allows connections, initially obtained outside a transaction, to be automatically enlisted when subsequently used during a transaction¹. With lazy enlistment, a new connection is enlisted in a transaction only if it is actually used in the transaction - when data is transmitted through the connection. Additional information/examples may be found on the Content from developer.jboss.org is not included.community wiki.

See Is it ok to use the CachedConnectionManager in a production JBoss environment in EAP 6) to note that lazy enlistment is enabled by default.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.