BTM

XAResourceManager incorrectly checking resource joinability

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.2
  • Fix Version/s: 1.3
  • Labels:
    None
  • Environment:
    JDK 1.6 on Linux
  • Number of attachments :
    1

Description

the method getManagedResourceWithSameRM calls isSameRM with the alreadyEnlistedHolderState.getXAResource(); should instead call with xaResourceHolderState..getXAResource().

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Riccardo Ferrucci added a comment -

Attached log file with BTM in debug, configuration properties file and spring configuration for test case datasources.

Show
Riccardo Ferrucci added a comment - Attached log file with BTM in debug, configuration properties file and spring configuration for test case datasources.
Hide
Permalink
Ludovic Orban added a comment -

See: http://www.nabble.com/Question-about-XAResourceManager-code-to17469695.html

This bug can only be triggered by recycling two different connections after transaction suspension, and in a very specific order.

Fixed in trunk and a new test has been created to make sure this cannot be left unnoticed anymore.

Show
Ludovic Orban added a comment - See: http://www.nabble.com/Question-about-XAResourceManager-code-to17469695.html This bug can only be triggered by recycling two different connections after transaction suspension, and in a very specific order. Fixed in trunk and a new test has been created to make sure this cannot be left unnoticed anymore.

People

  • Assignee:
    Ludovic Orban
    Reporter:
    Riccardo Ferrucci
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: