Directory Client API
  1. Directory Client API
  2. DIRAPI-199

LdapConnectionPool.getUnboundConnection is an oxymoron

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical 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

        Issue Links

          Activity

          lucas theisen created issue -
          lucas theisen made changes -
          Field Original Value New Value
          Link This issue relates to DIRAPI-200 [ DIRAPI-200 ]
          Hide
          lucas theisen added a comment -

          removed getUnboundConnection()

          revision: 1613509

          Show
          lucas theisen added a comment - removed getUnboundConnection() revision: 1613509
          lucas theisen made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Fix Version/s 1.0.0-M24 [ 12327371 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              lucas theisen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development