Uploaded image for project: 'TomEE'
  1. TomEE
  2. TOMEE-2561

Bad state in second connection to same datasource in same TX

Attach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment Visibility
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 7.0.6, 7.1.1, 8.0.0-M3
    • 7.0.7, 7.1.2, 8.0.1
    • None
    • None

    Description

      There's a case where, particularly if you're using XA, if you use a second connection to the same datasource in the same transaction, ManagedConnection will fetch the delegate transaction from the transaction registry, but the xaConnection and xaResource fields are dropped.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jgallimore Jonathan Gallimore
            jgallimore Jonathan Gallimore
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment