Announcement Announcement Module
No announcement yet.
transactional datasource with non-JTA transaction manager Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • transactional datasource with non-JTA transaction manager

    The following sentence is provided in the Spring reference documentation:

    If the DataSource, used by any non-JTA transaction manager, is looked up via JNDI and
    managed by a Java EE container, then it should be non-transactional because the Spring
    Framework, rather than the Java EE container, will manage the transactions.
    What could happen if transactional DataSource was used with a non-JTA Tx manager? Could it cause any problem in addition to the useless overhead costs caused by the JTA-transaction awareness of returned connections from the transactional data source?

  • #2
    Duplicate transactions (one managed by the app-server and one by spring)... Exceptions trying to start a new transaction to name 2.