Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-199

LdapConnectionPool.getUnboundConnection is an oxymoron

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.0-M24
    • Labels:
      None

      Description

      The unBind() operation, will close the session, thereby disconnecting, so you are effectively handing out an unconnected connection. This makes no sense. The best thing to do in this case is most likely to just hand out an already bound connection because that is the only guarantee we can make with a pool other than creating a new connection each time. When a connection is returned to the pool, we can just re bind() it so as to make sure that any changes made to the connection are reverted back to an initial state.

      Furthermore, an unBind() followed shortly thereafter by a bind() will eventually cause a race condition as described here

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ltheisen@mitre.org lucas theisen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: