Hi, We use apache commons pooling 1.6 in our enterprise application to pool LDAP connections. If the number of active connections in the pool is exhausted, the API is set to wait for 5 seconds before rejecting a connection request.
Now can someone please clarify about the order in which the connection object requests are served by the API at run time? Is it FIFO - by which I mean that the worker thread that requested for an active connection from the exhausted pool will get the first preference when a new connection object becomes available? Or is it LIFO, which is the vice versa? Please lemme know if I should clarify this further. Any light on this behavior is greatly appreciated. :) - Programmer. -- View this message in context: http://apache-commons.680414.n4.nabble.com/Commons-Pooling-request-queue-algorithm-tp4653914.html Sent from the Commons - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
