You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/01/08 20:53:27 UTC
[jira] Closed: (OPENEJB-300) transaction policy interceptors must
not enlist caller's connections
[ https://issues.apache.org/jira/browse/OPENEJB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-300.
---------------------------------
> transaction policy interceptors must not enlist caller's connections
> --------------------------------------------------------------------
>
> Key: OPENEJB-300
> URL: https://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: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira