tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENEJB-300) transaction policy interceptors must not enlist caller's connections
Date Mon, 30 Oct 2006 07:55:16 GMT
transaction policy interceptors must not enlist caller's connections
--------------------------------------------------------------------

                 Key: OPENEJB-300
                 URL: http://issues.apache.org/jira/browse/OPENEJB-300
             Project: OpenEJB
          Issue Type: Bug
          Components: container system
    Affects Versions: 2.2
            Reporter: David Jencks
         Assigned To: David Jencks
             Fix For: 2.2


Instance interceptors are all after the tx interceptors.  As a result, when a tx interceptor
starts a new tx, ConnectionTrackingCoordinator.newTransaction is called and attempt to enroll
any connection handles the CALLER has open in the new transaction.  These handles are not
going to be available to the called ejb so this is certainly wrong.

I think we can install a blank ConnectorInstanceContext in the CTC while the tx interceptors
are traversed.  The alternative would be to find some way to distinguish between container
and bean managed transactions inside the tx manager.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message