[OPENEJB-1062] StickyConnectionStrategy incorrectly caches connections

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Fix Version/s: 3.1.2
• Component/s: connectors
• Assignee: David Blevins
• Reporter: Dmitry Murashenkov
• Created: 22/Aug/09 11:13
• Updated: 10/Sep/09 08:09
• Resolved: 10/Sep/09 08:09

Description

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.