Sequence generation in a JTA environment should not require non-JTA datasource

• Key: OPENJPA-93
• Type: New Feature
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Patrick Linskey
• Reporter: Patrick Linskey
• Component/s: jdbc
• Fix Version/s: 0.9.7

Description

When obtaining non-transactional sequence numbers in a JTA environment when no non-jta-data-source or JDBC connection information is supplied, OpenJPA should suspend the current transaction, perform the sequence maintenance in a new transaction, commit, and resume the suspended transaction.

Comments

[Patrick Linskey]

svn r491147 includes code changes that have been tested in WebLogic Server. The feature is not yet documented. The behavior is as follows: if no non-JTA datasource is available and the current environment is managed, OpenJPA will suspend the current transaction, begin a new transaction, do the sequence work, commit, and resume the original transaction. This code makes some thread-safety assumptions that should be valid in a JTA environment, since JTA transactions are inherently thread-bound.

[Patrick Linskey]

Has anyone tested this on non-WLS appservers?

The feature works, but OPENJPA-149 currently prevents it from working in a WebSphere environment in a default configuration. See OPENJPA-149 for a workaround.