RFR : 8139965:Hang seen when using com.sun.jndi.ldap.search.replyQueueSize

[Roger Riggs]

Hi Sean,

Looks like a cleaner solution to synchronize writer and readers.

I don't quite understand the 80% capacity value.  It is related to the 
obsolete highWatermark
but that does not seem relevant with the update.

If the caller is going to specify a replyQueueCapacity then why should 
it be downgraded to 80%?

Roger



On 8/5/2016 10:05 AM, Seán Coffey wrote:
> Hoping to get a review on this issue that's been sitting on my plate 
> for a long while. Pavel drew up the bulk of the edits for this one 
> (Thanks)
>
> The fix basically delegates polling and timeout management to the 
> BlockingQueue.poll(timeout.. ) method. As a result it makes Connection 
> readReply logic much easier to handle.
>
> webrev : http://cr.openjdk.java.net/~coffeys/webrev.8139965.9/webrev/
> bug report : https://bugs.openjdk.java.net/browse/JDK-8139965
>