This content has been marked as final. Show 3 replies
"firstname.lastname@example.org" wrote:I searched the JCA and J2EE specs for this, but couldn't find anything backing this assumption. Do you per chance have some concrete reference for this?
JBoss assumes auto commit is true when the connection is first created,
as per spec.
188.8.131.52 Auto Commit
When a Connection is in an auto-commit mode, an Interaction, associated with the Connection, automatically commits after it has been executed. The auto-commit mode must be turned off if multiple interactions have to be grouped in a single transaction and committed or rolled back as a unit.
CCI does not provide explicit set/getAutoCommit methods in the Connection interface. This simplifies the application programming model for the transaction management.
A resource adapter must manage the auto-commit mode as follows:
A transactional resource adapter either at the XATransaction or
LocalTransaction level must set the auto-commit mode of Connection
instances participating in a transaction to off within the transaction. This
requirement holds for true both container-managed and bean-managed
A transactional resource adapter must set the auto-commit mode of Connection instances to on when used outside a transaction.
These requirements are independent of whether a transaction is managed as a local or XA transaction. A transactional resource adapter should implement this requirement in an implementation-specific manner.
A non-transactional resource adapter at the NoTransaction level, is not required to support the auto-commit mode for Connection.