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

CachedConnectionManager does not retain EJB context during transaction synchronizations

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: JBossAS-4.0.1 Final
    • Fix Version/s: No Release
    • Component/s: JCA service
    • Labels:
      None

      Description

      The CachedConnectionManager does not maintain the ejb context correctly
      for transaction synchronizations.

      If a connection is closed during afterCompletion(), it will use the caller's context
      to remove the connection from the list of unclosed connections.

      In fact, it is unsafe to be dealing with the ejb context during the transaction interceptor
      since this is outside the lock interceptor for entity beans meaning it won't be
      thread safe.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  adrian.brock Adrian Brock
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: