tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Blevins (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OPENEJB-1062) StickyConnectionStrategy incorrectly caches connections
Date Thu, 10 Sep 2009 08:09:57 GMT

     [ https://issues.apache.org/jira/browse/OPENEJB-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Blevins closed OPENEJB-1062.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.1.2
         Assignee: David Blevins

$ svn ci server
Sending        server/openejb-client/src/main/java/org/apache/openejb/client/ClusterMetaData.java
Sending        server/openejb-client/src/main/java/org/apache/openejb/client/ClusterResponse.java
Sending        server/openejb-client/src/main/java/org/apache/openejb/client/JNDIContext.java
Sending        server/openejb-client/src/main/java/org/apache/openejb/client/StickyConnectionStrategy.java
Sending        server/openejb-client/src/test/java/org/apache/openejb/client/MainTest.java
Adding         server/openejb-client/src/test/java/org/apache/openejb/client/OverlyStickyConnectionTest.java
Transmitting file data ......
Committed revision 813292.


> StickyConnectionStrategy incorrectly caches connections
> -------------------------------------------------------
>
>                 Key: OPENEJB-1062
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1062
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: connectors
>    Affects Versions: 3.1.1
>            Reporter: Dmitry Murashenkov
>            Assignee: David Blevins
>            Priority: Blocker
>             Fix For: 3.1.2
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Test case:
> 1. Create InitialContext (instance A) that connects to server 1. Lookup some bean there.
> 2. Create another InitialContext (instance B) that connects to server 2.
> In fact on the step 2 InitialContext instance B is connected to server 1. Because of
the following lines in the StickyConnectionStrategy:
> if (null != lastLocation && !failed.contains(lastLocation)) {
>     return connect(lastLocation); 
> }
> There is no check that server.getLocation() is equal to lastLocation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message