[jira] Created: (GERONIMO-2207) TransactionCachingInterceptor is returning the same ManagedConnection despite different ConnectionRequestInfo

["Jörg Heinicke (JIRA)" <de...@geronimo.apache.org>]

TransactionCachingInterceptor is returning the same ManagedConnection despite different ConnectionRequestInfo
-------------------------------------------------------------------------------------------------------------

                 Key: GERONIMO-2207
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2207
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: connector
    Affects Versions: 1.0
         Environment: Tomcat, Spring, Jencks, Geronimo Connector, Geronimo Transaction
            Reporter: Jörg Heinicke


(Thread at http://marc.theaimsgroup.com/?t=115323501500001&r=1&w=4)

In my use case the same javax.resource.cci.ConnectionFactory instance is asked twice for a connection with two different ConnectionSpec within one transaction. The symptom is that the TransactionCachingInterceptor returns the ManagedConnectionInfo of ManagedConnectionInfos.getShared() without any comparison of ConnectionRequestInfo, so I get a wrong ManagedConnection and a wrong Connection handle at the end.

David Jencks gave me the hint that I have to set my connections to "unshareable".

Aaron Mulder added:
Would it make sense for us to add some logic to the cache to segment the cache like we segment the pool?  That is, so if the cache notices that the pool is partitioned by connection request info, the cache would use the same logic before coughing up a shared connection?

David Jencks added:
I think we should seriously consider not forcing you to claim your connections are unshared.

-- 
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