Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1636

Don't try to delist a track-connection-by-tx connection that is already broken and has been closed.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBossAS-4.0.2 Final
    • JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1
    • None
    • None

    Description

      The transaction synchronization that returns track-connection-by-tx
      should not try to process connections that are broken and have already been
      closed.

      This leads to a spurious error message:
      org.jboss.resource.connectionmanager.TxConnectionManager - The re is something wrong with the pooling?
      java.lang.IllegalStateException: afterCompletion called with wrong tx!
      Expected: null, actual: TransactionImpl:XidImpl [...]
      at
      org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventLi
      stener$TxRemover.afterCompletion(TxConnectio
      nManager.java:588)

      The error message does not cause problems but it can be noisy/disconcerting in the logs.

      Attachments

        Activity

          People

            adrian.brock Adrian Brock (Inactive)
            adrian.brock Adrian Brock (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: