Working with multiple threads and Connectionpool in UnboundID LDAP

Question

Considering the huge load that I am getting for authentication, using multiple threads and Connectionpool will be a best solution to handle the load. However I have two design options in my mind

Pass Connectionpool to individual threads as argument and get a connection to do the bind request from ConnectionPool

Pass connection to threads rather than passing Connectionpool to threads and do bind request

Which Design would you prefer most and what are the reasons for them?

then how can I release the connection. What is the reason for it? — Malinda, Feb 28 '16 at 12:35

score 1 · Accepted Answer · answered Mar 01 '16 at 11:39

I found an answer for this question after a discussion happened with UnboundIDSDK forum. I will add the final finding for others. according to this It is recommended to available the pool to threads by passing the pool to thread as argument.

public BindResult doBind(LDAPConnectionPool pool, 
                     BindRequest bindRequest)
         throws LDAPException
{
 return pool.bind(bindRequest);
}

Working with multiple threads and Connectionpool in UnboundID LDAP

1 Answers1