Geronimo
  1. Geronimo
  2. GERONIMO-5824

jpa JTA transaction and missing jta-data-source should be warned about or rejected

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1.8, 2.2.2, 3.0.0
    • Fix Version/s: None
    • Component/s: persistence
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      Someone just had a lot of weird transaction errors that turned out to be because they had configured a persistence.xml with JTA transaction support and only a non-jta-datasource that was actually transactional. When both the tm and openjpa tried to control the tx confusion enused.

      We can detect this situation on deployment and either reject it or at least loudly warn about it.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development